Skip to main content
Glama

X420 agent services

x420_storm_date-finder

Read-onlyIdempotent

Storm date finder: Candidate storm dates for a point over up to 365 days, ranking each day by NEXRAD radar hail signatures (NOAA SWDI nx3hail) combined with NWS ground reports (hail size, wind gusts, tornadoes) from the IEM LSR archive. Sources: NOAA NCEI SWDI, NWS LSR via IEM. Heuristic ranking, not a date-of-loss determination. Not professional, legal, insurance, engineering, medical, financial or tax advice. Price: $0.10 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{candidate_dates, top_date, max_hail_in, max_wind_mph}, candidates[{date, radar{detections, max_size_in}, ground{hail_reports, max_hail_in, max_wind_mph, tornado_reports}, score}].

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_date-finder"
  }
}

Input Schema

NameRequiredDescriptionDefault
endNoYYYY-MM-DD end of window (default today)
latYeslatitude
lonYeslongitude
daysNo1–365 (default 365)
radius_kmNo1–50 (default 10)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior5/5

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

Annotations only say readOnly/openWorld/idempotent, but the description discloses the non-obvious behavior that actually governs a call: this hosted tool validates input and returns payment instructions rather than the deliverable, the price is $0.10 USDC via x402 on Base, and a local x420-mcp server can pay automatically. That is exactly the kind of context annotations cannot carry, and it is consistent with the readOnly, non-destructive hints.

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?

It is front-loaded with purpose, then caveats, pricing, payment mechanics, and the deliverable shape, so an agent can stop reading early once it has what it needs. It is dense but nearly every clause carries load; the legal/medical disclaimer sentence is boilerplate that could be trimmed or moved out of the primary flow.

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?

Despite no output schema, the description specifies the exact deliverable JSON structure (summary and candidates fields) and the full payment handshake, so an agent knows both what it will get and what it must do to get it. For a five-parameter, paid, stateless lookup, nothing operationally necessary is missing.

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 lat, lon, end, days and radius_km are already documented with defaults and ranges. The description adds only indirect hints — "for a point" and "up to 365 days" — and does not explain semantics like how radius_km affects scoring or how end interacts with days. Baseline 3 is appropriate when the schema does the work.

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 opening sentence names a specific verb and resource ("Candidate storm dates for a point") and states the ranking method — NEXRAD hail signatures from NOAA SWDI nx3hail combined with NWS LSR ground reports. That is far more than the name conveys and lets an agent distinguish it from sibling tools like x420_hail_point-history or x420_storm_reports on the basis of output shape (ranked candidate dates) rather than name alone.

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 description sets an important usage boundary — "Heuristic ranking, not a date-of-loss determination" — and gives detailed invocation steps (GET the url, read PAYMENT-REQUIRED, retry with PAYMENT-SIGNATURE). But it never says when to prefer this over the sibling storm/hail tools, nor what input conditions make the result meaningful (e.g. minimum window size or radius). Usage is implied by the deliverable, not contrasted with alternatives.

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