Nimbus Copiloto MCP Server
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
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| pingA | Verifica que el servidor MCP de Nimbus esta vivo. |
| listar_estados_de_ticketA | Lista los estados posibles de un ticket y su explicación. No toca la red, es una tool únicamente informativa, no devuelve los datos de un ticket específico sino de la lista de estados posibles y válidos que trabajamos en Nimbus. Casos de uso:
|
| consultar_ticketA | Consulta los datos de un ticket específico. Toca la red para obtener los datos. Únicamente lee información de un ticket, no modifica nada. Casos de uso:
Formato de código: TCK-0000 - Pudiendo ser los 0000 cualquier número. El código no distingue entre mayúsculas y minúsculas. |
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: ping checks server liveness, listar_estados_de_ticket provides reference information about ticket states, and consultar_ticket retrieves a specific ticket's data. There is no ambiguity or overlap between them.
Tool names follow a consistent verb_noun pattern (ping, listar_estados_de_ticket, consultar_ticket). Although 'ping' is a single verb, it is a standard convention and the other two follow the same style, ensuring predictability.
With 3 tools, the server is appropriately scoped for its narrow purpose of ticket status lookup and retrieval. Each tool is essential and there are no redundant or missing operations for the stated functionality.
The server covers the core read operations: checking health, listing possible ticket states, and fetching a specific ticket. A notable gap is the lack of a 'list_all_tickets' tool, but given the description, the server appears intentionally focused on individual ticket queries, so this is a minor omission rather than a critical failure.