redbus-mcp
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| buscar_ciudadesA | Busca ciudades/terminales de Perú en RedBus por nombre y devuelve su ID numérico. Necesario porque 'buscar_buses' funciona con IDs de ciudad. Devuelve también los terminales/áreas de cada ciudad. |
| buscar_busesA | Busca buses interprovinciales en Perú (vía RedBus) para una ruta y fecha. Acepta nombres de ciudad o IDs para origen/destino. Devuelve empresa, tipo de bus, horarios, duración, precios, asientos disponibles, calificación, punto de embarque/descenso y las amenidades, además de routeId/operatorId para consultar el detalle con 'detalle_servicio'. |
| detalle_servicioA | Devuelve el detalle de un servicio de bus concreto: mapa de asientos (número, tipo, precio, disponibilidad, piso) y puntos de embarque y descenso con horarios y direcciones. Requiere routeId, operatorId y los IDs de ciudad que entrega 'buscar_buses'. |
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 clearly distinct purpose: buscar_ciudades retrieves city IDs, buscar_buses searches for buses, and detalle_servicio gets detailed seat maps. No overlap or ambiguity.
All tools use Spanish and follow a verb_noun pattern except detalle_servicio which is noun_noun, creating a minor inconsistency. However, the naming is readable and descriptive.
Three tools cover the core data retrieval workflow (lookup city, search buses, get details) for a bus information service. The count is appropriate, though slightly minimal.
The tools support finding cities, searching buses, and obtaining seat details, but lack booking functionality and advanced filters. Coverage is adequate for basic search but incomplete for a full booking lifecycle.