Skip to main content
Glama

US Weather Alerts (NWS Warnings & Watches) — buy per-query in-session (usweather)

data_preview

Read-onlyIdempotent

✅ No API key needed. Listing: usweather: US Weather Alerts (NWS Active). Price 0.01 USDC/query (max 20 queries/session). Sample questions: Are there any active tornado, hurricane or flood warnings in the US right now?; What are the most recently issued NWS weather alerts?. FREE preview — no key, no payment. Try one of the sample questions now.

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

Input Schema

NameRequiredDescriptionDefault
slugNoPublic listing slug. Defaults to the routed session's listing when connected via /mcp/data/{slug}/http.
questionNoOptional free-text question you'd ask this data (echoed back).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds genuinely useful facts beyond that: no API key required, a 20-queries-per-session cap, and a stated price signal. However, the pricing language is muddled ('Price 0.01 USDC/query' alongside two separate 'FREE / no payment' claims), leaving the agent unsure whether calling incurs cost.

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

Conciseness2/5

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

The text opens with a checkmark emoji and a marketing restatement, then repeats the free/no-key claim three times in different phrasings. Two long sample questions crowd out the core explanation of what the tool returns, so the important information is not front-loaded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/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 full burden of explaining return values, yet it never says what comes back. The crucial constraint that only public metadata is returned (and that the 'question' is merely echoed back) lives only in the schema description, not in the tool description an agent scans first.

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 both the slug (defaults to the routed session's listing) and the optional question parameter are already fully documented in the schema. The description adds no further meaning about either parameter, so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a concrete listing ('usweather: US Weather Alerts') and implies a free trial call, but never states the actual operation: that it returns a guest-callable preview of public listing metadata rather than the weather data itself. An agent could reasonably read this as a tool that fetches NWS alerts. It also fails to distinguish itself from siblings like data_session_query or discover_agents, which likely retrieve the real data.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Sample questions hint at usage but describe what to ask the underlying listing, not when to call this tool versus data_session_query or data_session_open. There is no guidance on whether this is a pre-flight step before opening a paid session, and no stated exclusions.

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