Skip to main content
Glama

x420_hail_point-history

Retrieves NOAA SWDI hail signatures within a radius of a coordinate for the last N days, enabling roofing, claims, and property teams to screen recent storm exposure.

Instructions

Hail point history: Radar-detected hail signatures within a radius of a coordinate over the last N days (NOAA SWDI nx3hail). For roofing, claims and property agents that need a quick storm screen. PAID: $0.25 USDC per call, settled on Base via x402 from the wallet in X420_MCP_WALLET_PRIVATE_KEY (real money). Returns: JSON: detections, max size, days with hail, source URL - the deliverable plus X420's signed receipt and the settlement transaction. Example input: {"lat":"32.7357","lon":"-97.1081","radius_km":"5","days":"30"}.

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_hail_point-history"
  }
}

Input Schema

NameRequiredDescriptionDefault
latYeslatitude
lonYeslongitude
daysNo1–31, default 30
radius_kmNo0.5–25, default 5

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.2

TDQS

A4.4/5.0
Behavior5/5

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

Goes well beyond the annotations by disclosing that this is a PAID call at $0.25 USDC per call, settled on Base via x402 from a specific wallet env var, and flags that it is real money. The readOnlyHint=false / openWorldHint=true / idempotentHint=false annotations are consistent with a paid, external, non-idempotent (repeat calls cost again) operation, and the description explains why.

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?

Front-loads purpose, then payment, then returns, then example — a sensible order with little waste. The returns sentence is slightly tangled (a JSON list interleaved with receipt and settlement transaction), which costs a bit of clarity for a one-line description.

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 carries the return burden and does so by enumerating detections, max size, days with hail, source URL, plus the signed receipt and settlement transaction. Combined with payment mechanics and an example call, an agent has everything needed to invoke it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, and the description adds a complete example input that reveals the non-obvious detail that lat/lon/radius_km/days are passed as strings rather than numbers. It does not clarify what lat/lon coordinate frame or what happens at boundary values, but the example genuinely helps invocation.

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?

Names a specific verb and resource: radar-detected hail signatures within a radius of a coordinate over the last N days, and cites the upstream source (NOAA SWDI nx3hail). An agent can distinguish this from sibling storm tools such as x420_storm_reports or x420_storm_date-finder because the scope (point + radius + lookback window) is stated explicitly.

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?

Gives an audience and intent ("For roofing, claims and property agents that need a quick storm screen"), which implies when the tool is appropriate. However, it never names an alternative sibling or states a when-not condition, so the agent must infer how this differs from the other storm endpoints.

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