Skip to main content
Glama

Gate Help

gate_help

Retrieve full documentation for any Gate-MCP tool, use the recommended_stack playbook for navigation, or omit the tool name to view the documentation directory.

Instructions

Full docs for any Gate-MCP tool. tool='recommended_stack' for navigation playbook; omit for directory.

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": "gate_help"
  }
}

Input Schema

NameRequiredDescriptionDefault
toolNoTool name to get docs for, or omit for directory

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.12

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description must carry the behavioral burden, and it does disclose the two distinct return behaviors: a directory listing when the parameter is omitted and a playbook for the recommended_stack value. It omits whether the output is truncated, paginated, or how large docs entries are, which keeps it below a 5 for a no-annotation tool.

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

Conciseness5/5

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

Two short clauses, front-loaded with the purpose and then the parameter branching, with zero filler or restated title. Every phrase carries information an agent needs.

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?

For a single optional parameter help tool with full schema coverage and no output schema, this is nearly complete: it explains both call shapes and the special sentinel value. The only gap is a hint about what the returned docs contain or how to follow up after reading them.

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?

Schema coverage is 100% and the schema already says 'Tool name to get docs for, or omit for directory', so most of the description's parameter sentence duplicates structured data. The one genuinely added fact is that 'recommended_stack' is a special sentinel value with playbook semantics, which the schema does not explain.

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

Purpose4/5

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

The description names the resource precisely ('Full docs for any Gate-MCP tool'), which lets an agent distinguish this documentation lookup from the sibling tools that actually perform work (gate_graph_query, gate_invoke, etc.). It stops short of a full 5 because the verb is nominal ('docs') rather than an explicit 'returns documentation for'.

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

Usage Guidelines4/5

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

It gives concrete routing: set tool='recommended_stack' when you want the navigation playbook, and omit the parameter to get the directory. That covers both call modes clearly, but it never states the general when-to-use condition (e.g. 'call this before invoking a tool you are unsure about'), so an agent must infer the primary use case.

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