Weather 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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| fetch-WeatherC | Get the 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 ambiguity or overlap between tools. The tool has a distinct purpose of fetching weather data for a location.
Since there is only one tool, naming consistency is inherently perfect. The tool name 'fetch-Weather' follows a verb-noun pattern, though the capitalization is inconsistent, but this does not affect the score due to the single-tool context.
A single tool for a weather server is too few for the apparent scope, as it lacks basic operations like forecasts, historical data, or location searches. This minimal set limits functionality and is not well-scoped for typical weather-related tasks.
The tool surface is severely incomplete for a weather domain, covering only current weather fetching. There are significant gaps, such as missing forecasts, alerts, or multi-location queries, which will likely cause agent failures in broader weather-related workflows.