Echorune Radar MCP Server
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_weatherA | Live weather for any place on earth, including the radar echo drawn as text characters rather than an image: current conditions, a short forecast, a 2-hour rain sparkline, and a character radar map with the measured motion of the echo. |
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 possibility of confusing it with another tool. The purpose of get_weather is unambiguous.
get_weather uses a clear verb_noun convention, but with only one tool there is no recurring pattern to evaluate. No inconsistent naming exists to penalize.
A single tool is on the thin side for a server labeled as a radar MCP server. It is not unreasonable for a focused weather/radar lookup, but it falls below the typical 3-15 tool range.
The tool covers current conditions, short forecast, rain sparkline, and radar motion, which is solid for a combined weather/radar query. Missing pieces like alerts or historical radar are minor gaps rather than fatal omissions.