Skip to main content
Glama

x420_storm_reports

Retrieve NWS local storm reports (hail, wind, tornado, flood) within a radius and date window around a coordinate to review recent ground observations.

Instructions

Storm ground reports: NWS Local Storm Reports (hail, wind, tornado, flood ground reports from spotters, officials and the public) within a radius of a coordinate over up to 365 days, from the Iowa Environmental Mesonet archive of NWS LSRs (free, no key). Source: NWS LSR via IEM. Not a damage determination. Not professional, legal, insurance, engineering, medical, financial or tax advice. PAID: $0.05 USDC per call, settled on Base via x402 from the wallet in X420_MCP_WALLET_PRIVATE_KEY (real money). Returns: JSON: summary{hail, wind, tornado, flood, days}, reports[{ts, type_text, magnitude, unit, city, county, source, remark, distance_km}] - the deliverable plus X420's signed receipt and the settlement transaction. Example input: {"lat":"32.7357","lon":"-97.1081","radius_km":"25","days":"240"}.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "lat": "<lat>",
      "lon": "<lon>"
    },
    "name": "x420_storm_reports"
  }
}

Input Schema

NameRequiredDescriptionDefault
endNoYYYY-MM-DD end of window (default today)
latYeslatitude
lonYeslongitude
daysNo1–365 (default 90)
radius_kmNo1–100 (default 25)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.2

TDQS

A3.8/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Beyond the annotations, the description discloses the non-obvious cost model (PAID: $0.05 USDC per call, settled on Base via x402 from X420_MCP_WALLET_PRIVATE_KEY, real money) and that the deliverable includes a signed receipt and settlement transaction. It also exposes the data source and the 'not a damage determination' caveat, which annotations cannot carry. Minor gap: it does not state latency or failure/refund behavior for a paid call.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose is front-loaded in the first sentence, followed by source, disclaimers, payment terms and return shape. The long legal/medical disclaimer block is boilerplate that crowds the middle, but the return-value enumeration and example are substantive rather than filler.

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?

There is no output schema, and the description fully compensates by enumerating the JSON return shape (summary counters and per-report fields ts/type_text/magnitude/unit/city/county/source/remark/distance_km) as well as the receipt and settlement transaction. Combined with the payment mechanics and an example input, an agent has everything needed to call and interpret this tool.

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%, so the schema already documents lat, lon, radius_km (1–100, default 25), days (1–365, default 90) and end. The description adds only corroboration of the 365-day cap plus a concrete example input that shows all parameters used together; the example is mildly useful but does not explain new semantics.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific resource (NWS Local Storm Reports: hail, wind, tornado, flood ground reports) and a specific scope (within a radius of a coordinate, up to 365 days, from the IEM archive). It is unambiguous what data comes back, but it never distinguishes itself from the similarly-named sibling x420_hail_point-history or x420_storm_date-finder, so an agent must infer which storm tool to pick.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The usage context is implicit but reasonably clear: query storm ground reports near a lat/lon over a window, and the 'Not a damage determination' line sets a boundary on interpretation. There is no explicit when-to-use versus when-to-prefer-an-alternative guidance and no mention of the related hail/date-finder siblings.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.