Skip to main content
Glama

x420_storm_date-finder

Find candidate storm dates for a location over up to 365 days, ranked by radar hail signatures and NWS ground reports.

Instructions

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. PAID: $0.10 USDC per call, settled on Base via x402 from the wallet in X420_MCP_WALLET_PRIVATE_KEY (real money). Returns: 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}] - the deliverable plus X420's signed receipt and the settlement transaction. Example input: {"lat":"32.7357","lon":"-97.1081","radius_km":"10","days":"365"}.

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 observedv1.0.2

TDQS

A3.9/5.0
Behavior5/5

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

Beyond the annotations, the description discloses that each call costs $0.10 USDC settled on Base via x402 from a named wallet env var, that this is real money, and that the response includes a signed receipt and settlement transaction in addition to the data. It also characterizes the ranking as heuristic and disclaims decision-grade use. This is exactly the kind of cost, payment, and output-contract 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, sources, caveat, payment terms, return shape, and an example are all front-loaded and information-dense with little filler. The legal/medical/financial disclaimer sentence is boilerplate but plausibly required. Slightly long as a single block, but no sentence is wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/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 correctly supplies the return structure (summary, candidates, radar/ground breakdown, score) plus receipt and settlement fields. The main remaining gap is how 'days' and 'end' interact when both are given, which an agent would need to know to call it correctly.

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/radius_km are already documented, including the ranges. The description adds a concrete worked example showing string-typed coordinates and defaults, but does not explain precedence when both 'end' and 'days' are supplied. Baseline 3 is appropriate when the schema does the heavy lifting.

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 opening clause states a specific verb and resource: candidate storm dates for a point over up to 365 days, ranked from NEXRAD hail signatures plus NWS LSR ground reports. The data sources and the 'heuristic ranking, not a date-of-loss determination' caveat make the output's nature unambiguous. It does not explicitly differentiate itself from plausible siblings like x420_storm_reports or x420_hail_point-history, which keeps it below a 5.

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?

Usage is implied by the scenario described (find candidate dates for a location), and the disclaimer clarifies what the result should not be used for. However, there is no explicit when-to-use/when-not-to-use guidance and no named alternative for related needs such as pulling specific storm reports or point hail history.

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