MCP Weather Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ACCUWEATHER_API_KEY | Yes | Your AccuWeather API key, obtained by registering at the AccuWeather API website |
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_hourly_weatherC | Get hourly 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 1 tool
With only one tool, there is no possibility of ambiguity or overlap between tools. The single tool has a clear and distinct purpose, making it impossible for an agent to misselect between multiple options.
The single tool name follows a consistent verb_noun pattern (get_hourly_weather). Since there is only one tool, there are no deviations or mixed conventions to evaluate, resulting in perfect consistency.
A single tool for a weather server is too few for the apparent scope, as it only provides hourly forecasts without coverage for current conditions, daily forecasts, or other common weather data. This minimal set limits functionality and will likely cause agent failures in broader weather-related tasks.
The tool surface is severely incomplete for a weather domain, lacking obvious gaps such as current weather, daily forecasts, alerts, or historical data. With only hourly forecasts, agents cannot perform comprehensive weather-related operations, leading to significant limitations in coverage.