Polyform

geo_severe_weather_scan

Read-only

Severe weather scan (bundle) — One call: active NWS watches/warnings/advisories for a US state or point, summarized by severity with a CLEAR / MONITOR / CAUTION / AVOID operations verdict and the highest active event. For logistics, field ops and travel automation. Pass state (e.g. TN) or lat+lon. Price: $0.03 USDC (Base, via x402).

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": {
      "state": "<state>",
      "lat": "<lat>",
      "lon": "<lon>"
    },
    "name": "geo_severe_weather_scan"
  }
}

Input Schema

Name	Required	Description
`lat`	Yes	latitude (alternative to state)
`lon`	Yes	longitude (alternative to state)
`state`	Yes	US state code, e.g. TN

Schema Changelog

Changes observed during successful MCP inspections.

AddedSep 4, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false; the description adds useful behavioral context: it consults active NWS alerts, returns a severity summary and verdict, and costs $0.03 USDC. Nothing in the description contradicts the annotations.

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

Conciseness5/5

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

Three compact sentences with no filler: the scan scope, output verdict, intended use cases, input alternatives, and price are each one clause. The decision-critical information is front-loaded.

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?

For a read-only scan without an output schema, it conveys enough retrieval semantics: active NWS alerts, US state or point, severity summary, verdict, and highest event. It could be more explicit that coordinate mode requires both lat and lon despite the schema's required flags, but the description suffices for tool selection and invocation.

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 baseline is 3; the description adds 'Pass state (e.g. TN) or lat+lon', which signals coordinates must be paired together. However, the input schema marks all three parameters as required, so the description and schema conflict on whether state OR coordinates are sufficient, weakening the value this adds.

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

Purpose5/5

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

Description states a specific verb and resource: one call for active NWS watches/warnings/advisories for a US state or point, summarized by severity with a CLEAR / MONITOR / CAUTION / AVOID verdict and the highest active event. This clearly differentiates it from sibling weather_alerts, which is a plain alert tool, by emphasizing the bundle and operational verdict.

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

Usage Guidelines4/5

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

Explicitly frames usage contexts: logistics, field ops, and travel automation, which tells an agent when the bundle is relevant. It does not name alternatives or say when not to use it, so it stops short of the highest bar.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Polyform tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?