Skip to main content
Glama

Weather alerts (10 sats L402 or $0.01 USDC x402)

get_weather_alerts
Read-only

Active NWS alerts for a US point, city, ZIP, or state=XX (US only) — use this to check warnings. Price: 10 sats (Lightning) or $0.01 USDC on Base (x402). Sample (illustrative, not live): {"status":"success","endpoint":"weather_alerts","data":{"coverage":"us","source":"noaa_nws","count":1,"alerts":[{"event":"Wind Advisory","severity":"Moderate","headline":"Wind Advisory in effect until 6 PM CST","onset":"2026-11-15T12:00:00-06:00","expires":"2026-11-15T18:00:00-06:00"}]},"metadata":{"cost_sats":10}} Pay: Call it, get HTTP 402 (or MCP payment_required) with a Lightning invoice and macaroon, pay the invoice, then retry with Authorization: L402 <macaroon>:<preimage>. Or pay in USDC on Base via x402: sign the 402's x402 requirement (PAYMENT-REQUIRED header, or accepts in the JSON body) and retry with the PAYMENT-SIGNATURE (x402 v2) or X-PAYMENT (v1) header; only a 200 is settled.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_weather_alerts"
  }
}

Input Schema

NameRequiredDescriptionDefault
qNoSame as location: US city or ZIP.
latNoLatitude (−90 to 90). Use with lon.
lonNoLongitude (−180 to 180). Use with lat.
zipNo5-digit US ZIP code.
stateNoUS state or territory code (alerts only), e.g. TX.
locationNoUS city ('Austin, TX') or 5-digit ZIP. Alias: q.
x402_paymentNoOptional x402 payment (USDC on Base): base64 PaymentPayload (v2, or v1 X-PAYMENT format) signed for accepts[0] of this tool's payment_required result. Alternative to params._meta['x402/payment']. Omit both to receive the payment requirements.
l402_credentialNoOptional L402 credential '<macaroon>:<preimage_hex>' (or 'L402 <macaroon>:<preimage>') from a paid invoice or an active subscription. Omit it to receive the Lightning invoice and macaroon.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / x402_payment
      Added value: +{
      +  "description": "Optional x402 payment (USDC on Base): base64 PaymentPayload (v2, or v1 X-PAYMENT format) signed for accepts[0] of this tool's payment_required result. Alternative to params._meta['x402/payment']. Omit both to receive the payment requirements.",
      +  "type": "string"
      +}
  2. Added

TDQS

A4/5.0
Behavior5/5

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

Annotations only declare readOnlyHint and openWorldHint; the description adds the full paid-access behavior that an agent cannot infer: the price (10 sats or $0.01 USDC on Base), the 402 handshake with a Lightning invoice and macaroon, the retry header format, the x402 PAYMENT-SIGNATURE/X-PAYMENT variants, and the crucial settlement rule 'only a 200 is settled.' This is exactly the behavioral 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.

Conciseness3/5

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

The purpose is front-loaded and the payment instructions are actionable, but the inline sample JSON occupies a large share of the text for an illustrative, explicitly non-live payload, and the price is repeated in both the title and the body. A tighter structure would move the sample out and keep the 402/x402 steps, which are the load-bearing part.

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?

For an 8-parameter, zero-required, payment-gated tool with no output schema, the description covers purpose, geography limits, cost, the complete payment and retry flow, and the shape of a successful response. Nothing an agent needs in order to call it and get a settled 200 is missing.

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 description adds meaning beyond the schema by tying l402_credential and x402_payment to the acquisition flow: call first, receive a 402 with requirements, pay, then retry with the credential. That sequencing is not stated in the schema fields themselves. The location inputs (point via lat/lon, city, ZIP, state=XX) are restated rather than extended.

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 first clause names a specific resource and scope: 'Active NWS alerts for a US point, city, ZIP, or state=XX (US only)', and adds 'use this to check warnings.' An agent can distinguish this from get_weather_current or get_weather_forecast because the resource is alerts, not observations or forecasts. It stops short of naming a sibling, so it is clear but not maximally differentiated.

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 guidance is limited to the parenthetical 'use this to check warnings' plus the 'US only' constraint. There is no when-not guidance and no named alternative for non-US locations or for general conditions, so the agent must infer that current/forecast tools cover those cases. The extensive payment guidance is procedural, not about tool selection.

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