Skip to main content
Glama
pilot-training-rag

pilot-training-rag

by fmanso

get_page_content

Fetches exact page text from a pilot-training document by doc_id and page range, such as '12-14', so agents can read cited passages instead of generated prose.

Instructions

Texto de un rango de páginas, p. ej. pages='12-14'.

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>",
      "pages": "<pages>"
    },
    "name": "get_page_content"
  }
}

Input Schema

NameRequiredDescriptionDefault
pagesYes
doc_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/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 disclosure burden, and it discloses almost nothing beyond 'returns text'. It does not say whether pages are 1-indexed, whether there is a maximum range size or truncation, or what happens for out-of-range pages. Return shape is partly covered by the existing output schema, which limits the damage somewhat.

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 short sentence, front-loaded with the resource and followed by the most useful usage example; nothing is wasted. It sits close to under-specification rather than conciseness, but no wording is redundant.

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 2-required-parameter retrieval tool with no annotations and no schema descriptions, the definition is thin: the meaning of doc_id, the page indexing base, range limits, and failure behavior are all absent. The output schema covers return values, but the call-side semantics remain largely unexplained.

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 description coverage is 0%, with both parameters bare strings. The description compensates well for 'pages' by giving the accepted syntax and an example ('12-14'), which is real added meaning. It says nothing at all about 'doc_id', so half the parameter surface remains undocumented.

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 a specific resource and scope: raw text for a range of pages, which an agent can distinguish from whole-document or chunk retrieval in principle. It stops short of naming any sibling (get_chunk, get_document_structure) to make that contrast explicit.

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 statement of when to use this instead of get_chunk, search_corpus, or get_document_structure, and no prerequisites (for example whether the document must first be processed/OCR'd). The only implicit hint is the page-range example, which shows how to call it rather than when.

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