Update mcp README.md tools list

[fredzqm]

This is generated by:

npx firebase-tools experimental:mcp --generate-tool-list

[gemini-code-assist]

Summary of Changes

Hello @fredzqm, I'm Gemini Code Assist¹! 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 updates the src/mcp/README.md file to accurately reflect the current suite of Firebase tools. It provides a more comprehensive description for the AI assistant tool, introduces a new build tool for Data Connect, and adds a range of new functionalities for managing Crashlytics issues. Additionally, it refines the categorization and descriptions of existing Realtime Database tools, ensuring the documentation remains up-to-date and informative.

Highlights

• Enhanced AI Assistant Description: The description for the firebase_consult_assistant tool has been significantly expanded to detail its capabilities in providing information, best practices, troubleshooting, code examples, and contextual help across various Firebase services.
• New Data Connect Tool: A new tool, dataconnect_build, has been added to facilitate compiling Firebase Data Connect schemas, operations, and connectors, and checking for build errors.
• Expanded Crashlytics Toolset: Several new Crashlytics-related tools have been introduced, allowing for more granular management of issues, notes, sample crashes, and listing top devices, operating systems, and versions.
• Realtime Database Tool Refinements: The 'Feature Group' for Realtime Database tools has been updated from 'realtime database' to 'database', and their descriptions have been slightly rephrased for conciseness.

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

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 👍 and 👎 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.

Footnotes

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. ↩

[gemini-code-assist]

Code Review

This pull request updates the list of available tools in the MCP server's README. The changes include adding several new tools for Data Connect and Crashlytics, updating the description for firebase_consult_assistant to be more detailed, and adjusting the descriptions for the database tools. While the more detailed description for the assistant is a great improvement, I've found significant inconsistencies between the tool names and descriptions in the README and their implementation in the code. I've also suggested improvements to the database tool descriptions for clarity and consistency. Please see my detailed comments.

[gemini-code-assist]

The updated descriptions for the database tools are less clear and grammatically inconsistent with the rest of the table. For example, "Get an RTDB database's rules" is awkward, and all four descriptions are missing a trailing period.

For better readability and consistency, I suggest revising them to be more descriptive, like the previous versions.

Suggested change

	| database_get_data | database | Returns RTDB data from the specified location |
	| database_set_data | database | Writes RTDB data to the specified location |
	| database_get_rules | database | Get an RTDB database's rules |
	| database_validate_rules | database | Validates an RTDB database's rules |
	| database_get_data | database | Returns RTDB data from the specified location. |
	| database_set_data | database | Writes RTDB data to the specified location. |
	| database_get_rules | database | Retrieves the security rules for the database. |
	| database_validate_rules | database | Validates the security rules for the database. |