MCP API 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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| obtener-climaC | Herramienta para obtener clima |
| crear-usuarioB | Crea un nuevo usuario con nombre, apellido y DNI |
| listar-usuariosB | Lista todos los usuarios registrados en el sistema |
| crear-empresaC | Crea una nueva empresa con todos los datos requeridos |
| listar-empresasB | Lista todas las empresas registradas en la API |
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 5 tools
The tools are mostly distinct, with clear separation between company and user operations. However, 'obtener-clima' (get weather) is an outlier that could cause confusion about the server's primary domain, as it doesn't relate to the company/user management focus of the other tools.
Four of the five tools follow a consistent Spanish verb_noun pattern (crear-empresa, crear-usuario, listar-empresas, listar-usuarios). 'obtener-clima' also follows this pattern but uses a different verb ('obtener' vs 'crear/listar'), which is a minor deviation that maintains readability.
Five tools is a reasonable count, but the inclusion of 'obtener-clima' makes the scope feel borderline. The core company/user management domain has good coverage with four tools, but the weather tool seems out of place, suggesting either an incomplete or overly broad scope.
For the apparent company/user management domain, there are significant gaps. While create and list operations exist for both entities, there are no update, delete, or get-by-id tools, which are essential for full CRUD coverage. The weather tool adds confusion rather than addressing these gaps.