mcpapp1
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_alertsA | Get weather alerts for a US state. Args: state: Two-letter US state code (e.g. CA, NY) |
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 misselection. The tool's purpose is clearly defined in its name and description.
The single tool name follows the verb_noun pattern (get_alerts), which is clean and predictable. There are no other tools to create inconsistency.
One tool feels thin for a server, even one dedicated to weather alerts. While alerts retrieval is a focused task, a small set of supporting tools (e.g., list states or get alert details) would make the server feel more complete.
For the stated purpose of retrieving weather alerts, the get_alerts tool covers the core operation without obvious gaps. The domain is narrow, and no additional lifecycle operations are necessary for read-only alert access.