mcp-fastapi
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| buscar_documentosA | Busca documentos de referência do FastAPI por tópico/palavra-chave. |
| obter_documentoA | Obtém o conteúdo completo de um documento de referência pelo seu id. |
| listar_documentosA | Lista todos os documentos de referência do FastAPI disponíveis. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
Each tool has a distinct purpose: searching by keyword, retrieving by ID, and listing all documents. There is no overlap or ambiguity between them.
All tool names follow a consistent verb_noun pattern in Portuguese (buscar_documentos, obter_documento, listar_documentos), with the expected singular/plural distinction for retrieving single vs. multiple items.
Three tools is perfectly scoped for a documentation retrieval server. Each tool covers a fundamental operation without unnecessary bloat.
The set covers the full lifecycle of read-only document access: search, list, and retrieve by ID. There are no obvious gaps for the server's stated purpose.