Skip to main content
Glama

X420 agent services

x420_weather_alerts

Read-onlyIdempotent

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. Price: $0.02 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: count, alerts[{event, severity, certainty, urgency, headline, area, effective, expires, description, instruction}].

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 observed

TDQS

A4.2/5.0
Behavior5/5

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

Annotations already declare readOnly/openWorld/idempotent/non-destructive, and the description adds substantial behavior the annotations cannot: $0.02 USDC per call on Base, the x402 challenge flow (GET url, read PAYMENT-REQUIRED from the 402, retry with PAYMENT-SIGNATURE), and the local-server alternative. The 'does NOT return the deliverable' disclosure is exactly the kind of consequence an agent must know before calling.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Purpose and the critical payment caveat are front-loaded and clear, but the disclaimer sentence ('Not professional, legal, insurance... advice') is filler, and the payment instructions are packed into a dense, hard-to-scan run of abbreviations and protocol terms.

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 compensates by enumerating the deliverable's JSON fields (event, severity, certainty, urgency, headline, area, effective, expires, description, instruction). Remaining gaps are minor: coordinate format and bounds, plus error behavior for non-US or invalid coordinates.

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 coverage is 100%, so lat/lon are already documented, and the description adds useful constraint meaning: the coordinate must be a US coordinate. It adds nothing about the string format (decimal degrees vs degrees/minutes) or expected precision, which matters because both params are typed as strings.

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 clause names a specific resource and scope: 'NWS active alerts: Active National Weather Service watches, warnings and advisories covering a US coordinate'. An agent can tell this apart from x420_weather_forecast by the resource (active alerts vs. forecast) without opening either schema.

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?

It gives essential context for when to call it: it is free at the source ('no key') and covers US coordinates only. Most importantly, the description says this hosted tool does NOT return the deliverable and only returns payment instructions, which steers invocation correctly. It does not explicitly compare against the forecast sibling or say when not to use alerts.

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