Skip to main content
Glama

Paid public-data feeds (x402, 0.002 USD)

Active US National Weather Service alerts in one call, severe and extreme first: event, severity, area, headline, onset,

weather_alerts
Read-onlyIdempotent

Active US National Weather Service alerts in one call, severe and extreme first: event, severity, area, headline, onset, expires, sender (area=two-letter state, severity=Severe|Extreme|Moderate, count up to 50). One poll replaces watching NWS. Pay per call $0.002 USDC on Base via x402.

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": "weather_alerts"
  }
}

Input Schema

NameRequiredDescriptionDefault
areaNotwo-letter US state
countNoup to 50
severityNoExtreme, Severe, Moderate
x_paymentNosigned x402 payment (X-PAYMENT header value); omit on the first call to receive the price and payment requirements

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, open-world, non-destructive semantics, so the description earns credit for the extras it supplies: results are ordered severe/extreme first, the count is capped at 50, and each call costs $0.002 USDC on Base via x402, which is a real operational constraint not carried by annotations. It stops short of describing empty-result or error behavior.

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?

Two densely packed sentences with the scope, returned fields, and ordering front-loaded before the cost note. Some of the parenthetical parameter restatement duplicates the schema, but nothing is gratuitous.

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 does the necessary work of listing returned fields and their ordering, and it discloses the payment flow at a high level (details live in the x_payment schema entry). Minor gaps remain around defaults and empty/error outcomes for a tool that bills per call.

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%, so all four parameters are already documented. The description restates the same semantics (two-letter state for area, Severe|Extreme|Moderate for severity, count up to 50) without adding format or default-value detail, so it sits at the baseline.

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 description names the resource (active US National Weather Service alerts) and its scope (US only, active only), and enumerates the returned fields (event, severity, area, headline, onset, expires, sender) plus the sort order. There is no explicit verb, but the operation (fetch active alerts) and its result set are unambiguous, and no sibling tool overlaps this domain.

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?

"One poll replaces watching NWS" implies the intended use case (a single-shot pull instead of repeated polling), but there is no explicit when-not guidance, no mention of what to do when no alerts are active, and no comparison to any alternative tool.

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