MCP Servers
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 |
|---|---|
| get-current-weatherC | Get current weather for a location |
| get-forecastC | Get 5-day weather forecast for a location |
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 2 tools
The two tools have clearly distinct purposes: one provides current weather data, while the other provides a 5-day forecast. There is no overlap or ambiguity between them, making it easy for an agent to select the correct tool based on the time horizon needed.
Both tool names follow a consistent verb_noun pattern with hyphens (get-current-weather, get-forecast). The naming is predictable and readable, with no deviations in style or convention across the set.
With only 2 tools, the server feels thin for a weather domain, as it lacks operations like historical data, alerts, or location search. While the tools cover basic current and forecast needs, the count is borderline low for typical agent workflows that might require more comprehensive weather data.
The server provides core current and forecast functions, but there are notable gaps for a weather service, such as no historical weather data, severe weather alerts, or location autocomplete. Agents can work around this for basic queries, but the surface is incomplete for more advanced use cases.