Skip to main content
Glama

TridentStack Control Docs

Read a TridentStack doc

get_doc
Read-only

Return the full markdown of a single documentation chunk by its id (from a search_docs result). Only ids present in the index are valid; this never fetches arbitrary URLs.

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": {
      "id": "<id>"
    },
    "name": "get_doc"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesA doc id from search_docs, e.g. guide:rings#phases

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint=false and destructiveHint=false, so safety is covered. The description adds genuinely new behavioral context: the return is the full untruncated markdown body, and the tool 'never fetches arbitrary URLs', reassuring the agent that ids cannot be used to reach outside the index. It omits error behavior for invalid ids and any size limits.

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 tight sentences with the return value front-loaded and the id-validity caveat following immediately; every clause carries information and nothing is repeated from the title.

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 one-parameter read tool with full schema coverage and clear annotations, this covers what an agent needs, including the return format (full markdown). Only edge-case behavior — what happens on a stale or invalid id — is left unstated.

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 'id' property already documents its source ('A doc id from search_docs') and an example format ('guide:rings#phases'). The description largely restates that provenance, adding only the validity constraint, so the baseline 3 applies.

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?

States a precise verb and resource — 'Return the full markdown of a single documentation chunk by its id' — and pins the granularity to a single chunk, which cleanly separates it from search_docs and list_docs. The provenance of the id ('from a search_docs result') further anchors it as a fetch-by-id retrieval rather than a discovery tool.

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?

The parenthetical '(from a search_docs result)' plus 'Only ids present in the index are valid' effectively tell the agent to obtain ids via search first and that arbitrary or guessed ids will not resolve. There is no explicit when-not-to-use statement or a named alternative for bulk listing, so it stops short of full routing guidance.

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