Model Context Protocol (MCP) Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GROQ_API_KEY | No | API key for accessing Groq services | |
| OPENAI_API_KEY | No | API key for accessing OpenAI services | |
| ANTHROPIC_API_KEY | No | API key for accessing Anthropic services |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get-alertsC | Get weather alerts for a US state |
| get-forecastB | Get weather forecast for a location in the US |
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 tools get-alerts and get-forecast have clearly distinct purposes: one provides weather alerts, the other gives forecasts. No overlap.
Both tool names follow the consistent pattern 'get-<resource>', using lowercase and hyphens, which is predictable.
With only 2 tools, the server feels too sparse for a weather domain. Typically, more operations like current conditions or radar would be expected.
The tool set only covers alerts and forecasts, missing common weather operations like current conditions, location search, or severe weather warnings, resulting in significant gaps.