Skip to main content
Glama

get_context_document

Read-only

Get a built-in documentation topic by name (see list_context_topics).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "topic": "<topic>"
    },
    "name": "get_context_document"
  }
}

Input Schema

NameRequiredDescriptionDefault
topicYesArgomento della documentazione (da list_context_topics).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / topic / description
      Added value: +"Argomento della documentazione (da list_context_topics)."
  2. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds that topics are a built-in, fixed set whose names come from another tool, but says nothing about what the response looks like (raw text, sections, truncation) or error behavior for an unknown topic.

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?

A single front-loaded sentence with no filler, and the sibling pointer is appended efficiently. There is room for one more clause of behavioral detail without becoming verbose.

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

Completeness3/5

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

For a one-parameter read tool with full schema coverage and helpful annotations, the definition is minimally sufficient; no output schema means the description could have said what a 'document' returns. Nothing outright wrong is missing, but the definition is thin.

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 single 'topic' parameter is already documented in the schema (in Italian) as coming from list_context_topics. The description only repeats that sourcing hint and adds no format, case-sensitivity, or fallback guidance.

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?

States a specific verb and resource: fetch one built-in documentation topic by name, which distinguishes it from list_context_topics (which enumerates them). The only softness is 'built-in documentation' — it does not say what domain the docs cover.

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?

The parenthetical '(see list_context_topics)' implies the discovery-then-fetch workflow, which is useful routing guidance. It does not state when this should be preferred over other documentation-like siblings (e.g. get_aplus_document, get_sop), nor any exclusions.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources