F
licenseNot graded
qualityD
maintenanceProvides real-time weather information for any location using FastMCP.
-
echorune radar
Server Details
Live weather anywhere, with the radar drawn as text characters, not an image.
If you are the author of this connector, you can claim ownership with GitHub, an HTTP challenge, or a DNS record. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
- Status
- Healthy
- Uptime
- 60.1% over 41 days
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-06-18
- URL
- Repository
- eirik-rune/runemap
- GitHub Stars
- 3
- Server Listing
- Echorune Radar MCP Server
TDQS
A4.3/5.0
Scored across 1 tool
Disambiguation5/5
With only one tool, there is no possibility of confusing it with another. The purpose is clearly described and self-contained.
Naming Consistency5/5
The single tool name follows a clear verb_noun pattern and is immediately readable. Since there is only one tool, there are no naming conflicts or mixed conventions.
Tool Count3/5
One tool is at the low end of the range and the server feels thin for a radar-focused service. The tool bundles many features, so it may be intentional, but the surface is still minimal.
Completeness4/5
The tool covers current conditions, forecast, precipitation trend, and radar map, which covers the core use case well. More granular radar controls or alerts would be nice, but their absence is not a critical gap.
Available Tools
1 toolget_weatherWeather scene with a text radar mapARead-onlyIdempotentInspect
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.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| lang | No | Language of the reply. Default en. | |
| place | Yes | Place name (any language) or 'lon,lat' with longitude first, e.g. tokyo, 清迈, or 139.7,35.7 |
TDQS
A4.3/5.0
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already indicate read-only and idempotent behavior. The description adds that the radar is drawn as text characters, which is an output format detail not covered by annotations. No side effects or limitations are mentioned, but none are expected given the simple weather lookup.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is concise, using a single well-structured sentence with a colon to list deliverables. No redundant words or excessive detail.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness5/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool's simplicity (2 parameters, no output schema, no nested objects), the description fully covers what the user receives. No missing context for typical usage.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters3/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100% for both parameters (place and lang). The description does not add extra parameter semantics beyond the schema, which is acceptable per the rubric's baseline for high coverage.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose5/5
Does the description clearly state what the tool does and how it differs from similar tools?
Clearly states it provides live weather for any place, with a specific mention of the radar echo rendered as text characters. The description fully conveys the tool's purpose without ambiguity.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines4/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
Implies usage by describing what the tool returns (current conditions, forecast, sparkline, radar map). Since there are no sibling tools, explicit differentiation is unnecessary, but a direct 'when to use' statement would slightly improve clarity.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
1 tool update
- First observed
get_weather
Related MCP Connectors
Get US weather forecasts, active alerts, and current observations.
Free, keyless real-time weather and 7-day forecasts for any city worldwide.
Weather data, forecast API, climate data, historical weather, alerts, agricultural & travel weather.
Smarter Weather MCP: forecasts, alerts, outlooks, observations, AQI, grids, and map imagery.
Related MCP Servers
- AlicenseAqualityDmaintenanceReal-time weather, forecasts, astronomy, marine data for 200+ countries2119 npm1MIT
- AlicenseNot gradedqualityAmaintenanceGet US weather forecasts, active alerts, and current observations via the National Weather Service API.293 npm1Apache 2.0
- FlicenseBqualityDmaintenanceProvides real-time US weather alerts and forecasts using the National Weather Service API.2-
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd
Glama MCP Gateway
Add one secure layer between your agents and this server.