Skip to main content
Glama
pilot-training-rag

pilot-training-rag

by fmanso

get_chunk

Fetch a document chunk plus its neighboring chunks to restore context around a citation from FAA, ICAO or EASA pilot-training sources.

Instructions

Devuelve un fragmento y sus contiguos (más contexto).

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": {
      "chunk_id": "<chunk_id>"
    },
    "name": "get_chunk"
  }
}

Input Schema

NameRequiredDescriptionDefault
chunk_idYes
neighboursNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.8/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden and mostly does not meet it. It discloses that neighbour chunks are returned, but says nothing about boundary behavior at document edges, what happens if chunk_id is invalid, or whether the neighbour count applies per side.

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

Conciseness3/5

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

A single short sentence with no wasted words, so it is concise, but it is under-specified rather than tight. The most useful information, the context-widening behavior, is relegated to a parenthetical.

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 retrieval tool with zero annotation coverage, no output schema, and zero parameter documentation, a one-line description is well short of what an agent needs. It omits return shape, boundary handling, and parameter meaning, all of which fall to the description by default here.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must compensate and does not. The word "contiguos" vaguely gestures at the neighbours parameter, but neither parameter is explained: neither chunk_id semantics nor whether neighbours counts one side or both, nor its clamping rules, is stated.

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 ("Devuelve un fragmento") and adds the key beyond-the-name detail that contiguous neighbours are included for extra context. It does not, however, distinguish this from siblings like get_page_content, which retrieves content at a different granularity.

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 "(más contexto)" implies the intended usage: call this when a bare chunk is insufficient and surrounding context is wanted. There is no explicit when-not guidance and no named alternative, so an agent must infer the routing decision.

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