MCP Template
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_weatherB | Retrieves weather forecast information from the National annotations Weather Service API for the specified location. The location should be in the format of latitude,longitude (e.g., '47.7623,-122.2054'). |
| get_alertsA | Retrieves all currently active weather alerts, warnings, and advisories issued by the National Weather Service for the specified state. This includes severe weather warnings, flood advisories, winter weather alerts, and more. |
| get_forecastA | Retrieves a multi-period weather forecast from the National Weather Service for the specified coordinates. The forecast includes temperature, wind conditions, and detailed descriptions for the next 5 forecast periods (typically covering the next 2-3 days). |
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 3 tools
The tools 'get_forecast' and 'get_weather' have significant overlap in purpose, as both retrieve weather forecast data from the National Weather Service for a location. The descriptions are similar, with 'get_forecast' specifying multi-period details and 'get_weather' being more general, which could cause confusion for an agent trying to select the appropriate tool. 'get_alerts' is distinct, focusing on active warnings rather than forecasts.
All tool names follow a consistent 'verb_noun' pattern using snake_case: 'get_alerts', 'get_forecast', and 'get_weather'. There are no deviations in naming conventions, making the set predictable and easy to parse for an agent.
With 3 tools, the count is borderline for a weather service server. It feels thin, as it lacks operations like updating or managing alerts, or providing historical data, which might be expected for a more comprehensive weather API. However, it covers basic retrieval needs, so it's not severely mismatched.
Inferring the domain as weather data access, there are significant gaps in the tool surface. The server only provides retrieval operations (get_alerts, get_forecast, get_weather) with no create, update, or delete capabilities, and it lacks tools for other common weather functions like radar data, historical trends, or location-based searches beyond coordinates. This incompleteness could lead to agent failures when more advanced operations are needed.