Skip project, TOS, and auth checks for mocked tools

[samedson]

Description

These shouldn't trigger because we likely don't have a project in scope

[gemini-code-assist[bot]]

Summary of Changes

Hello @samedson, I'm Gemini Code Assist[^1]! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request addresses an issue where mocked tools might incorrectly trigger project, Terms of Service, or authentication checks, leading to failures in environments where a full project context is not available or necessary. By explicitly disabling these checks for mocked tools, the change ensures that these tools can operate as intended without requiring a complete Firebase project setup or user authentication, thereby improving the reliability and functionality of testing and evaluation processes.

Highlights

• Mocked Tool Configuration: Updated the configuration for mocked tools to explicitly skip project, TOS, and authentication checks.
• Metadata for Mocked Tools: Introduced a _meta property within the mcp object of mocked tools, setting optionalProjectDir, requiresProject, requiresAuth, and requiresGemini to false.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with :thumbsup: and :thumbsdown: on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

[^1]: Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.