Skip to main content
Glama
pilot-training-rag

pilot-training-rag

by fmanso

search_corpus

Search an indexed Spanish/English corpus of FAA, ICAO, and EASA pilot-training and simulation documents to retrieve citable excerpts with exact references.

Instructions

Busca en el corpus (castellano o inglés) y devuelve fragmentos citables.

Args: query: pregunta o palabras clave, en cualquier idioma. k: número de fragmentos (1-20). doc_ids: opcional, limita a esos documentos.

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": {
      "query": "<query>"
    },
    "name": "search_corpus"
  }
}

Input Schema

NameRequiredDescriptionDefault
kNo
queryYes
doc_idsNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations at all, the description carries the full disclosure burden; it does add real value by saying results come back as citable fragments and that both Spanish and English content are covered. It says nothing about ranking, permissions, cost, or what happens when doc_ids filters exclude everything, which leaves meaningful behavioral gaps for an unannotated tool.

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?

One front-loaded sentence states purpose and return shape, followed by a compact Args block that adds value rather than restating the schema. No filler or repetition; the only minor cost is that the Args list is the bulk of the text.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool is a simple three-parameter search and the description covers purpose, language scope, return form, and every parameter; since an output schema exists it need not explain return values. What remains missing is any routing guidance relative to the sibling tools, which is the main gap for an agent deciding what to call.

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

Parameters4/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 it does document all three parameters: query as a question or keywords in any language, k with its 1-20 range (information absent from the schema), and doc_ids as an optional restriction to specific documents. Only the default of k=8 goes unmentioned, keeping it just under a 5.

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 ("Busca en el corpus") plus the return type ("fragmentos citables") and notes the corpus is Spanish or English. It does not distinguish itself from siblings such as lookup_citation or get_chunk, which could plausibly return similar citable fragments, so it stops short of a 5.

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?

Usage is only implied: the description makes clear this is the entry point for finding material in the corpus, but it never says when to prefer it over lookup_citation or get_chunk, nor any exclusions. An agent must infer the retrieval-vs-citation workflow.

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