Skip to main content
Glama

x420_weather_alerts

Retrieve active National Weather Service watches, warnings, and advisories for a US latitude/longitude, returning structured JSON alert details for weather-risk checks.

Instructions

NWS active alerts: Active National Weather Service watches, warnings and advisories covering a US coordinate (free, no key). Source: NOAA/NWS api.weather.gov. Not professional, legal, insurance, engineering, medical, financial or tax advice. PAID: $0.02 USDC per call, settled on Base via x402 from the wallet in X420_MCP_WALLET_PRIVATE_KEY (real money). Returns: JSON: count, alerts[{event, severity, certainty, urgency, headline, area, effective, expires, description, instruction}] - the deliverable plus X420's signed receipt and the settlement transaction. Example input: {"lat":"32.7357","lon":"-97.1081"}.

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_weather_alerts"
  }
}

Input Schema

NameRequiredDescriptionDefault
latYeslatitude
lonYeslongitude

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.2

TDQS

A3.8/5.0
Behavior4/5

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

Goes well beyond the annotations by disclosing real behavioral facts: it costs $0.02 USDC per call settled on Base via x402, requires the wallet key in X420_MCP_WALLET_PRIVATE_KEY, and returns a signed receipt plus settlement transaction. This usefully explains why readOnlyHint=false on an otherwise read-shaped call. It does not cover failure modes such as a failed settlement or partial results.

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, cost, credential, and return shape are front-loaded in a compact block, and the example is genuinely useful. It is somewhat run-on, and the liability disclaimer sentence, while defensible for a paid public-data tool, adds bulk for the agent.

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 carries the return contract and does so explicitly, enumerating count and each alert field, plus receipt and settlement transaction. Missing only edge-case behavior (invalid coordinate, settlement failure, whether alerts are empty vs error), which keeps it short of complete.

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, but the example input {"lat":"32.7357","lon":"-97.1081"} adds real meaning the schema lacks: values are decimal-degree strings with negative longitudes, within a US bounding area. That is more than a restatement of 'latitude'/'longitude'.

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 concrete verb+resource: 'Active National Weather Service watches, warnings and advisories covering a US coordinate,' naming the source api.weather.gov. It implicitly separates itself from x420_weather_forecast by focusing on active alerts, but never names that sibling or draws the contrast 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?

Usage is only implied: the 'US coordinate' scoping tells an agent this is not usable for non-US locations, and the alert framing hints at it versus forecast. There is no explicit when-to-use/when-not statement and no reference to the forecast sibling as the alternative for predictive data.

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