docs: add tools style guide

[averikitsch]

Description

Should include a concise description of the changes (bug or feature), it's
impact, along with a summary of the solution

PR Checklist

Thank you for opening a Pull Request! Before submitting your PR, there are a
few things you can do to make sure it goes smoothly:

• Make sure you reviewed
  CONTRIBUTING.md
• Make sure to open an issue as a
  bug/issue
  before writing your code! That way we can discuss the change, evaluate
  designs, and agree on the general idea
• Ensure the tests and linter pass
• Code coverage does not decrease (if any source code was changed)
• Appropriate docs were updated (if necessary)
• Make sure to add ! if this involve a breaking change

🛠️ Fixes #<issue_number_goes_here>

[gemini-code-assist]

Summary of Changes

Hello, 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 introduces a new style guide document aimed at standardizing the development of Model Context Protocol (MCP) tools within the MCP Toolbox. The guide provides essential principles and best practices to enhance tool quality, improve agent reasoning, maintain security, and ensure consistent API design, ultimately leading to more precise and efficient tool interactions.

Highlights

• New Documentation: Introduced a comprehensive style guide for developers building MCP (Model Context Protocol) tools using MCP Toolbox.
• Tool Development Best Practices: The guide outlines best practices for tool quality, including focusing on outcomes, separating read/write operations, ensuring idempotency, and providing actionable error messages.
• Naming Conventions & API Clarity: Defined clear naming conventions for tool names (snake_case) and toolset names (kebab-case), along with guidelines for simple primitives, flat arguments, and pagination in APIs.
• Security Guidelines: Emphasized security best practices such as "secure by default" configurations, using tool descriptions as guidance, and preventing data exfiltration.

Changelog

• docs/en/concepts/style-guide.md
  • Added a new document outlining style guidelines and best practices for MCP tool development.

Activity

• No human activity has been recorded on this pull request yet.

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 👍 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 introduces a new style guide for developing MCP tools. The document is comprehensive and well-structured, providing valuable guidelines for developers. I have one minor suggestion to improve the grammar for better clarity.

[github-actions]

🔎 Preview at https://googleapis.github.io/genai-toolbox/previews/PR-2577/

[github-actions]

🔎 Preview at https://googleapis.github.io/genai-toolbox/previews/PR-2577/

[github-actions]

Link Resolution Note

Local links and directory changes work differently on GitHub than on the docsite. You must ensure fixes pass the GitHub check and also work with hugo server.
See Link Checking and Fixing with Lychee for more details.

Summary

Status	Count
🔍 Total	0
✅ Successful	0
⏳ Timeouts	0
👻 Excluded	0
❓ Unknown	0
🚫 Errors	0
⛔ Unsupported	0

No links were found. This usually indicates a configuration error.
If this was expected, set 'failIfEmpty: false' in the args.
Full Github Actions output

[github-actions]

🔎 Preview at https://googleapis.github.io/genai-toolbox/previews/PR-2577/

[github-actions]

🧨 Preview deployments removed.