Skip to main content
Glama
orzcls

Gemini CLI MCP Server

by orzcls

Help

Access help information for using the Gemini CLI MCP Server to interact with Google's Gemini CLI, analyze files, handle large contexts, and execute code safely.

Instructions

receive help information

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The switch case handler for the 'Help' tool within the CallToolRequestSchema handler. It returns a static text content block listing all available tools and their descriptions.
    case "Help":
        return {
            content: [{
                type: "text",
                text: "Gemini CLI MCP Tool - Fixed Version\n\nAvailable commands:\n- ask-gemini: Interact with Gemini CLI\n- ping: Test connection\n- Help: Show this help\n- brainstorm: Generate novel ideas with creative frameworks\n- fetch-chunk: Retrieve cached chunks from changeMode responses\n- timeout-test: Test timeout prevention"
            }]
        };
  • The 'Help' tool definition in the tools array, which is returned by ListToolsRequestSchema. Includes name, description, and empty input schema. This serves as the tool registration.
    {
        name: "Help",
        description: "receive help information",
        inputSchema: {
            type: "object",
            properties: {},
            required: []
        }
    },
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure but offers minimal insight. 'receive help information' implies a read-only operation but doesn't specify what kind of help (e.g., general guidance, error messages, usage tips), how it's delivered, or any constraints like rate limits. It lacks crucial context for safe and effective use.

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 extremely concise with just two words, which is appropriate for a simple tool. However, it's arguably under-specified rather than efficiently informative, as it doesn't convey enough meaning to be truly helpful. It earns a 4 for brevity but loses a point for lacking substance.

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 tool's simplicity (0 parameters, no output schema), the description is incomplete. It doesn't explain what 'help information' entails, how it might be structured, or when it's useful compared to other tools. For even a basic tool, this leaves significant gaps in understanding its role and output.

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 0 parameters, and schema description coverage is 100%, so there's no need for parameter documentation in the description. The baseline for this scenario is 4, as the description appropriately doesn't waste space on non-existent parameters.

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 is provided or what resource it accesses. It doesn't distinguish this tool from potential siblings like 'ask-gemini' or 'brainstorm' that might also provide assistance. The purpose remains vague rather than specific.

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?

The description provides no guidance on when to use this tool versus alternatives like 'ask-gemini' or 'brainstorm'. There's no mention of context, prerequisites, or exclusions. This leaves the agent with no information to make an informed choice among sibling tools.

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/orzcls/gemini-mcp-tool-windows-fixed'

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