Said 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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| obtener-climaC | Herramienta para obtener el clima en tiempo real |
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 1 tool
With only one tool, there is no possibility of ambiguity or overlap between tools, as there are no other tools to compare it against. The single tool's purpose is clearly defined for obtaining real-time weather.
Since there is only one tool, it inherently has perfect consistency with itself. The naming follows a clear verb-noun pattern in Spanish ('obtener-clima'), which is straightforward and predictable.
A single tool is generally too few for a meaningful server scope, as it limits functionality and suggests an incomplete or overly narrow implementation. While it might suffice for a minimal weather service, it lacks the depth expected for typical MCP servers.
Inferred domain is weather data, but the tool surface is severely incomplete. It only provides real-time weather retrieval without supporting operations like forecasts, historical data, or location-based queries, which are common in weather APIs, leading to significant gaps.