Skip to main content
Glama

Agent Exchange store

signals_alerts

$0.002 via x402: Active US weather alerts from NOAA (api.weather.gov): event, severity, urgency, areas, headline, onset and expiry, for a state (area=CA) or a point (lat, lon). Pay 0.002 USDC through https://store.agentexchange.work/gw/signals/alerts?area=CA Via the Agent Exchange store gateway; settled by Coinbase.

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

Input Schema

NameRequiredDescriptionDefault
latNolat
lonNolon
areaNotwo-letter US state, e.g. CA (default: all active alerts, first 100)
limitNo1..200, default 50
x_paymentNoSigned x402 payment payload (optional; without it the answer is the price)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does quite well: it discloses the cost ($0.002 / 0.002 USDC), the x402 payment mechanism, the settlement provider (Coinbase), and the gateway URL. It omits rate limits and the exact behavior of the optional x_payment parameter, but the paid-operation profile is well communicated.

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?

Reasonably sized and front-loaded with the price, but it is a run-on sentence and repeats the price ('$0.002' and '0.002 USDC') plus the gateway path that already encodes the endpoint. Some redundancy costs it a point.

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?

Despite no output schema and no annotations, the description lists the returned fields (event, severity, urgency, areas, headline, onset, expiry) and explains the payment flow, which covers most of what an agent needs. Missing only pagination/limit semantics and exclusions.

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 the schema itself documents lat, lon, area, limit, and x_payment. The description only reinforces the area and lat/lon usage already in the schema, adding no format or constraint detail beyond it. 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 verb+resource: 'Active US weather alerts from NOAA (api.weather.gov)', and even enumerates the returned fields (event, severity, urgency, areas, headline, onset, expiry). It is easily distinguished from non-weather siblings (signals_quakes, signals_hn, signals_federal_register), though it does not explicitly contrast with weather_forecast.

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?

It implies usage by showing both query modes ('for a state (area=CA) or a point (lat, lon)'), but there is no explicit when-to-use, when-not, or named alternative for the weather-alerts-vs-forecast decision. Usage is inferable rather than stated.

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