Skip to main content
Glama

Help

Access help information for the Gemini MCP Tool to understand how to use its features for analyzing files and codebases with natural language commands.

Instructions

receive help information

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The 'Help' tool implementation, including name, description, schema reference, and execute handler that runs the 'gemini -help' command.
    export const helpTool: UnifiedTool = {
      name: "Help",
      description: "receive help information",
      zodSchema: helpArgsSchema,
      prompt: {
        description: "receive help information",
      },
      category: 'simple',
      execute: async (args, onProgress) => {
        return executeCommand("gemini", ["-help"], onProgress);
      }
    };
  • Zod schema definition for the Help tool arguments (empty object, no parameters required).
    const helpArgsSchema = z.object({});
  • Registration of the helpTool into the central toolRegistry array.
    toolRegistry.push(
      askGeminiTool,
      pingTool,
      helpTool,
      brainstormTool,
      fetchChunkTool,
      timeoutTestTool
    );
Behavior1/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. 'receive help information' reveals nothing about how the tool behaves—whether it provides documentation, examples, troubleshooting, or something else; what format the help comes in; or any operational constraints. This is inadequate for a tool with zero annotation coverage.

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

Conciseness3/5

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

The description is extremely concise—just three words—but this brevity comes at the cost of being under-specified rather than efficient. It's front-loaded in the sense that there's only one phrase, but it fails to convey meaningful information, so it doesn't fully earn its place as helpful content.

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

Completeness2/5

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

Given the lack of annotations and output schema, the description is incomplete for a tool that presumably provides some form of assistance. It doesn't explain what the help entails, how it's returned, or any context about its function relative to siblings, leaving significant gaps in understanding for the agent.

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

Parameters4/5

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

The tool has zero parameters, and the input schema has 100% description coverage (though empty). The description doesn't need to add parameter semantics, so it meets the baseline expectation for a parameterless tool. No additional value is provided, but none is required.

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

Purpose2/5

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

The description 'receive help information' is a tautology that essentially restates the tool name 'Help' without specifying what kind of help or how it's delivered. It doesn't distinguish this from sibling tools like 'ask-gemini' or 'brainstorm', leaving the agent to guess what this tool actually does beyond the obvious implication of providing help.

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

Usage Guidelines1/5

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

There is no guidance on when to use this tool versus alternatives like 'ask-gemini' or 'brainstorm'. The description provides no context about appropriate scenarios, prerequisites, or exclusions, leaving the agent with no usage direction beyond the vague notion of seeking help.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/jamubc/gemini-mcp-tool'

If you have feedback or need assistance with the MCP directory API, please join our Discord server