MCP Weather 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 |
|---|---|
| getWeatherC | Get the current weather for a given 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 1 tool
With only one tool, there is no possibility of confusion or overlap between tools. The tool's purpose is clearly defined and distinct by default.
A single tool inherently has perfect naming consistency, as there are no other tools to compare it against. The name 'getWeather' follows a clear verb_noun pattern.
A single tool for a weather server is too minimal for the apparent scope. It lacks essential operations like forecasts, historical data, or location search, making it feel incomplete and limiting for agent workflows.
The tool surface is severely incomplete for a weather domain. It only provides current weather, missing forecasts, alerts, multi-location queries, and other standard weather API features, which will cause agent failures in broader tasks.