Skip to main content
Glama

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

data_session_query

Optional paid queries — competing is free. Listing: usweather: US Weather Alerts (NWS Active) at 0.01 USDC per query (max 20 queries/session). Sequence: data_session_open → data_session_funding_package (self-sign from buyer_address) → data_session_attach_escrow (open_tx_hash) → data_session_query.

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": {
      "session_id": "<session_id>",
      "query": "<query>"
    },
    "name": "data_session_query"
  }
}

Input Schema

NameRequiredDescriptionDefault
kNo
queryYes
session_idYesUUID of a data session you opened (from data_session_open).
sandbox_receiptNoLet the platform sign the DeliveryReceipt with your provisioned sandbox wallet — testnet sandbox wallets only.
delivery_receiptNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior4/5

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

The description adds substantive behavior not in the annotations: a per-query cost of 0.01 USDC, a cap of 20 queries per session, and the escrow prerequisite that makes it non-idempotent. Since readOnlyHint=false but destructiveHint=false, the cost-debit context is exactly the kind of disclosure that matters. It stops short of describing what happens on failure or after the 20-query cap.

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 sequence is front-loaded and useful, but the opening clause "Optional paid queries — competing is free" is ambiguous and the sentence is dense with pricing and listing detail. Little is redundant, but the emphasis is misplaced relative to what an agent needs to invoke this specific tool.

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

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Pricing, session cap, and prerequisite chain give solid coverage for a paid query tool with no output schema. The remaining gap is parameter-level: k and delivery_receipt are undefined, and the description does not say what a successful response contains or how one query is charged.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 40%, so the description should compensate, but it explains none of the five parameters directly. It mentions open_tx_hash (a parameter of a sibling tool) and buyer_address, but says nothing about query content limits, the k result count, delivery_receipt, or sandbox_receipt, leaving two parameters undocumented in both places.

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 talks about "Optional paid queries" and names the specific listing (usweather: US Weather Alerts) with a price, and the closing step of the sequence is data_session_query, so the purpose can be inferred. But it never states the verb and resource directly, as the schema's own description does ("Run a prepaid query against a funded data session"), and the phrase "competing is free" muddies the point.

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?

The explicit tool sequence (open → funding_package with self-sign from buyer_address → attach_escrow with open_tx_hash → query) tells an agent precisely what must precede this call, which is real usage guidance. However, it gives no guidance on when to use this versus reading results back (e.g., data_session_queries) or what to do when a session is exhausted or unfunded.

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