Skip to main content
Glama

X420 agent services

x420_hail_point-history

Read-onlyIdempotent

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. Price: $0.25 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: detections, max size, days with hail, source URL.

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 observed

TDQS

A4.1/5.0
Behavior5/5

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

Annotations already declare read-only, idempotent, non-destructive and open-world, and the description adds far more: it discloses that the hosted tool does NOT pay and does NOT return the deliverable, what it returns instead (pay_to, network, price, x402 URL), the exact payment flow (GET the url, read PAYMENT-REQUIRED from the 402, retry with PAYMENT-SIGNATURE under x402 v2), the $0.25 USDC on Base price, and the local-server alternative. This is unusually complete behavioral disclosure for a paywalled tool and directly prevents a failed first 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?

Front-loaded with the purpose, then the audience, then pricing and the payment protocol, which is the order an agent needs. It is fairly dense but every clause carries operational weight; the parenthetical source code and the deliverable summary are slight extras rather than waste.

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, so the description compensates by naming the returned fields (detections, max size, days with hail, source URL), and it fully specifies the multi-step payment handshake required to actually get data. For a paid, two-stage tool with four parameters, nothing an agent needs in order to invoke it correctly 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%, with lat, lon, days (1–31, default 30) and radius_km (0.5–25, default 5) all documented in the schema. The description restates the coordinate/radius/days concept but adds no syntax, format or unit detail beyond what the schema already supplies, so the baseline 3 applies.

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?

States a specific resource and scope: radar-detected hail signatures within a radius of a coordinate over the last N days, naming the NOAA SWDI nx3hail source. It is clear what the tool computes, but it does not distinguish itself from nearby siblings like x420_storm_reports or x420_storm_date-finder, leaving the agent to infer the difference from names alone.

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?

Gives an explicit audience and context ('For roofing, claims and property agents that need a quick storm screen'), which tells the agent this is a lightweight screening call rather than a full storm report analysis. There are no explicit when-not-to-use conditions or named alternatives, so it stops short of full routing guidance.

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