Skip to main content
Glama
pilot-training-rag

pilot-training-rag

by fmanso

get_document_structure

Retrieve a document's hierarchical section tree with page references and node summaries to navigate its structure and locate relevant content.

Instructions

Árbol de secciones del documento, con páginas y resumen de cada nodo.

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": {
      "doc_id": "<doc_id>"
    },
    "name": "get_document_structure"
  }
}

Input Schema

NameRequiredDescriptionDefault
doc_idYes
max_levelNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.3/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full burden, and it only discloses that results include page numbers and a per-node summary. It says nothing about read-only safety, size or depth of the tree, truncation, ordering, or error behavior for an invalid doc_id.

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 compact sentence with the resource front-loaded and no filler. It is efficient, though the extreme brevity is part of why the parameter and usage gaps exist.

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?

For a two-parameter tool with no annotations and no output schema, the description should explain the depth control and confirm the read-only nature; it does neither. It partially compensates by describing the returned tree, but leaves the caller without enough to invoke it correctly beyond the required doc_id.

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

Parameters1/5

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

Schema description coverage is 0% for both parameters, and the description mentions neither doc_id nor max_level. The most consequential parameter, max_level (default 3), which controls tree depth and therefore result size, is left completely unexplained.

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

Purpose3/5

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

The description names a specific resource ("Árbol de secciones del documento") and even characterizes the return shape (pages plus a summary per node), so an agent can tell it is a structural-outline reader rather than a content fetcher. However, there is no verb and no differentiation from siblings such as get_page_content or get_chunk, so the purpose is only implied by the noun phrase.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no exclusion of alternatives, and no stated prerequisites. An agent must infer from the phrase "árbol de secciones" that this is the tool for outline/structure discovery versus full text retrieval, which is guesswork rather than instruction.

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