sanalert-mcp
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| sanalert_levelA | SanAlert's level right now for one place in Poland, worked out on this computer: quiet, activity,
approaching or near, the website's sentence about it ( |
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
Only one tool exists, so there is no risk of selecting the wrong tool. Its description clearly defines a single purpose: retrieving SanAlert level and related alerts for a specified place in Poland.
The single tool name sanalert_level is descriptive, uses snake_case, and aligns with the server name. With only one tool, there is no inconsistent convention to compare.
A single tool is thin for an MCP server, even though the tool itself is comprehensive. The rubric treats 1-2 tools as borderline, and there is no ability to split concerns across multiple operations.
The tool covers current level, messages, and data trust for one place, but there is no way to discover valid town names or coordinates, nor to query multiple places or historical data. This is a notable gap for an agent that does not already know the exact input.