Skip to main content
Glama
pilot-training-rag

pilot-training-rag

by fmanso

list_documents

Lists available pilot-training documents with jurisdiction and chunk counts so agents can identify sources before searching or citing.

Instructions

Documentos disponibles, jurisdicción y número de fragmentos.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_documents"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

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 supplied, so the description carries the full behavioral burden, yet it discloses nothing about scope (all documents? filtered by access?), pagination, ordering, or whether the call is read-only. It mentions jurisdiction and chunk counts, which is useful signal about the payload shape, but an output schema already exists, so this adds little that is not already structured.

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 a single short fragment with no padding, which is good, but it is a verbless phrase rather than a front-loaded statement of purpose, and the switch to Spanish while tool names and siblings are English adds friction for an English-oriented agent. Brevity here reflects under-specification more than discipline.

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?

For a zero-parameter catalog tool with an output schema, little explanation is strictly required, so the definition is minimally adequate. Missing is any link to the sibling tools that consume document identifiers (get_document_structure, get_chunk), which is the main thing an agent needs to sequence calls.

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?

The tool takes zero parameters, so there is no parameter semantics to explain and the baseline of 4 applies. The empty object schema is self-explanatory and the description neither contradicts nor obscures it.

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 is a noun phrase ('Documentos disponibles, jurisdicción y número de fragmentos') rather than a verb+resource statement, so it reads as a summary of returned fields instead of a declared action. The name list_documents plus 'Documentos disponibles' lets an agent infer a listing of all available documents, but nothing distinguishes it from search_corpus or get_document_structure.

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 for query-based siblings like search_corpus, and no hint about when an agent should prefer this catalog view over fetching structure or page content. The agent must infer the intended call context entirely from the tool name.

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