Skip to main content
Glama
pilot-training-rag

pilot-training-rag

by fmanso

lookup_citation

Retrieve exact FAA, ICAO, and EASA pilot-training citations such as sections, appendices, and tables to locate precise source references instead of generated prose.

Instructions

Acceso estructural: '60.15', '§ 60.25(b)', 'App. A', 'Table A1B'.

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": {
      "citation": "<citation>"
    },
    "name": "lookup_citation"
  }
}

Input Schema

NameRequiredDescriptionDefault
citationYes

Output Schema

NameRequiredDescriptionDefault
resultYes

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 discloses almost nothing: it does not say whether lookup is exact-match or normalized, what happens on an unrecognized citation, or whether it resolves to a chunk or a document. An output schema exists, so return shape need not be explained, but the lookup behavior itself is opaque.

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?

It is short with no filler, but it is a bare fragment rather than a front-loaded purpose statement. The most important fact — what the tool returns — is absent, so brevity here reflects under-specification rather than discipline.

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 single-parameter lookup tool with an output schema, the description needs only to state the action and the accepted input forms. It supplies format examples but omits the action and any error or resolution semantics, leaving the definition materially incomplete.

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 0% for the single 'citation' parameter, so the description must compensate. It partially does by giving concrete accepted formats ('60.15', '§ 60.25(b)', 'App. A', 'Table A1B'), which is real added meaning, but it never states whether these are exhaustive, how section symbols or spacing are handled, or what an invalid form does.

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

Purpose2/5

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

The description never states a verb or what the tool actually does — it only says 'Acceso estructural' and lists citation format examples like '60.15', '§ 60.25(b)', 'App. A'. An agent must infer from the name that it resolves a citation to content. The examples are useful, but the purpose itself is left to the tool name.

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?

No when-to-use guidance is given, and no distinction is made from plausible siblings such as get_chunk, get_page_content, or search_corpus. The agent is not told whether this tool should precede or replace those alternatives.

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