Gemini MCP Server

Gemini MCP Help

gemini_help

Get help with Gemini MCP features, settings, and best practices for integrating Google Gemini into AI assistants.

Instructions

Get comprehensive help about Gemini MCP features, settings, and best practices

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "gemini_help"
  }
}

Input Schema

Name	Required	Description	Default
`topic`	No	Help topic to display	overview

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.3.0Jun 22, 2026

TDQS

A3.9/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations exist, so the description carries the burden. It correctly indicates the tool returns help information and does not have side effects. While it could mention output format (e.g., textual), it is adequate for a simple read-only tool. No contradictions found.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single concise sentence that front-loads the action and resource. It could be slightly more informative about the output, but it is not verbose and effectively communicates the core purpose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool has one optional parameter, no output schema, and no annotations, the description covers the essential purpose and usage. An agent can infer how to use it from the parameter enum. It is complete enough for a help tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has full coverage (100%) with a description for the 'topic' parameter. The tool description does not add extra meaning beyond the schema. At baseline, a score of 3 is appropriate since the schema already serves the purpose.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool provides help about Gemini MCP features, settings, and best practices. The verb 'get comprehensive help' and specific resource 'Gemini MCP' make the purpose unambiguous and distinct from sibling tools that perform tasks like image analysis or chat.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied (ask for help on a topic), but no explicit guidance on when to use this tool versus alternatives. Given many sibling tools, the description would benefit from stating that it is for learning or reference rather than performing actions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.