Skip to main content
Glama
pilot-training-rag

pilot-training-rag

by fmanso

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
PILOT_RAG_TRANSPORTNoTransport for the MCP server. Defaults to stdio; set to 'http' to use streamable-http.stdio

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

Corpus de instrucción de pilotos y simuladores (FAA, ICAO, EASA). Cita SIEMPRE con el campo 'path' del resultado: es la referencia exacta (p. ej. «14 CFR § 60.15(b)(1)» o «Doc 9995 › Chapter 3 › 3.1 BACKGROUND»). Si el resultado no cubre la pregunta, dilo en vez de completar de memoria.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}

Tools

Functions exposed to the LLM to take actions

NameDescription
list_documentsC

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

search_corpusA

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.

get_chunkC

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

lookup_citationC

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

get_document_structureC

Árbol de secciones del documento, con páginas y resumen de cada nodo.

get_page_contentC

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

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

B3.2/5.0

Scored across 6 tools

Disambiguation4/5

The tools are mostly clearly separated by purpose: corpus search, citation lookup, chunk retrieval, document listing, structure browsing, and page extraction. There is minor overlap between get_chunk and get_page_content as context-expansion tools, and between search_corpus and lookup_citation as retrieval paths, but descriptions make the intended use reasonably clear.

Naming Consistency5/5

All tool names follow a consistent snake_case verb_noun pattern: list_documents, search_corpus, get_chunk, lookup_citation, get_document_structure, get_page_content. The verb choices vary appropriately by action while maintaining a predictable convention.

Tool Count5/5

Six tools is well-scoped for a RAG retrieval server. Each tool has a distinct retrieval role: discovery, search, chunk context, citation lookup, structure navigation, and page extraction.

Completeness4/5

The surface covers the core RAG retrieval lifecycle: discovering documents, searching, expanding chunks, resolving citations, inspecting structure, and reading page ranges. Minor gaps exist, such as no explicit document-level metadata retrieval beyond list_documents, but these are not likely to block most agent workflows.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues