Skip to main content
Glama

X420 agent services

x420_storm_reports

Read-onlyIdempotent

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. Price: $0.05 USDC per call (x402 on Base). This hosted tool does NOT pay and does NOT return the deliverable: it validates the input and returns payment instructions (pay_to, network, price and the x402 URL to pay at). GET the url; read PAYMENT-REQUIRED from the 402; retry with PAYMENT-SIGNATURE (x402 v2). Or run the local x420-mcp server with your own wallet key to pay automatically. Deliverable once paid: JSON: summary{hail, wind, tornado, flood, days}, reports[{ts, type_text, magnitude, unit, city, county, source, remark, distance_km}].

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 observed

TDQS

A4.4/5.0
Behavior5/5

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

Well beyond the annotations, it discloses the critical behavioral fact that the hosted tool does NOT return the deliverable and does NOT pay, only returning pay_to, network, price and the x402 URL, plus the exact retry sequence (GET url, read PAYMENT-REQUIRED from the 402, retry with PAYMENT-SIGNATURE). It also states the $0.05 USDC cost on Base and the free/no-key nature of the upstream data. This is exactly the kind of context annotations cannot carry.

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?

Purpose is front-loaded, then pricing, payment flow, and deliverable shape follow in a logical order. It is dense but each block earns its place in an x402 tool; the stacked liability disclaimers ('not a damage determination' plus the legal/insurance/medical list) are somewhat redundant boilerplate.

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?

With no output schema, the description supplies the deliverable shape (summary counts and reports array with ts, type_text, magnitude, unit, city, county, source, remark, distance_km), the payment protocol steps, and the data source. An agent knows both what it will get and what it must do to get it.

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, end, days and radius_km with defaults. The description only restates the range ('up to 365 days', 'within a radius'), adding no format hints or constraints beyond the schema, so the baseline 3 applies.

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?

The first sentence gives a specific resource (NWS Local Storm Reports: hail, wind, tornado, flood), a precise scope (within a radius of a coordinate, up to 365 days), and names the upstream archive (Iowa Environmental Mesonet). An agent can tell this apart from nearby siblings such as x420_hail_point-history or x420_storm_date-finder because the report types, spatial filter and date window are all stated.

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?

It clearly frames the operating context: this hosted variant only validates input and returns payment instructions, and the alternative is running the local x420-mcp server with your own wallet key for automatic payment. What it does not do is tell the agent when to pick this over sibling storm tools (e.g. hail-only history) or when a coordinate-radius search is inappropriate, so it is clear but not fully exclusive.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources