TrueFixR Storm Data API

Atlas United data, all datasets (advanced / multi-county)

get_weather_data

Read-only

CATCH-ALL and PAID-PULL tool. Prefer the dedicated tools below when one fits (get_storm_history: one county, past 365 days; get_risk_forecast: one county, next 24 hours to 10 days; get_address_report: one address, past 365 days; get_property_storm_history_report: one address, 2003 to present; get_current_weather: one point, now to 48 hours). Use THIS tool for: every PAID address-level pull (set addresses=true), county coverage, facilities, wildfire (county-level), at_risk, daily, a counties multi-county rollup (comma-separated, max 15), hazard_score, or any parameter the dedicated tools do not expose (radius_mi, date_of_loss, window, months, category, limit, kind, details, hours_ahead). Datasets: ML Storm Forecast by Address (risk), Model-Based Weather by Address (weather), Model-Based Hourly Forecast by Address (weather with hours_ahead), Storm History by Address: Reported and Radar-Detected Events Since 2003 (history), Past Storm Leads by Address: Reported and Radar-Detected, Last 365 Days (storms). addresses=false (default) is a FREE preview; addresses=true (or details=true for weather) returns the paid data and requires the user's own Atlas United Data API account key, or an x402 payment. Call with no arguments for the full menu. HARD RULE when called with no arguments: this returns the full menu. Output that entire raw response back to the user verbatim, every dataset, every field, every example. Do not summarize or paraphrase. A shortened version is wrong even if it looks complete.

Input Schema

Name	Required	Description	Default
`lat`	No	Latitude in decimal degrees.
`lon`	No	Longitude in decimal degrees.
`days`	No	Look-back window in days where supported.
`kind`	No	dataset=at_risk only. Narrows to 'schools' or 'businesses'.
`limit`	No	Max records on the real paid pull (default 2000, real per-dataset caps still apply -- e.g. storms caps at 5000).
`peril`	No	Storm/risk type filter. Used by dataset=storms and dataset=risk (narrows to one storm type -- use the exact names returned under storm_types in a free preview) and by dataset=at_risk (narrows to one peril bucket, a different real meaning -- check that dataset's own preview for its real values). Common storms/risk values: HAIL, THUNDERSTORM_WIND, FLASH_FLOOD, HEAVY_RAIN, FLOOD, TORNADO.
`state`	No	2-letter US state code, e.g. TX.
`county`	No	County name without the word 'County', e.g. Dallas.
`format`	No	Response format. json (default) or csv.	json
`months`	No	dataset=storms only. Returns month-bucketed history totals instead of individual leads, for the last N months.
`window`	No	dataset=risk only. Forecast window. Default 24h.
`address`	No	Street address, for dataset=address.
`dataset`	No	Target dataset. Default storms.
`details`	No	dataset=weather only (Model-Based Weather by Address). true = full current-conditions pull, billed $0.0002/call. false (default) = free lean response, no account needed. Equivalent to addresses=true for this dataset.
`category`	No	dataset=facilities only. Facility category filter.
`counties`	No	Comma-separated county names (max 15) plus state, for a multi-county rollup. Free preview only.
`addresses`	No	false = free preview. true = address-level records -- requires EITHER the user's own Atlas United Data API account key (Authorization header) OR an x402 payment (see x_payment param below); no account needed for the x402 path.
`radius_mi`	No	dataset=history only. Search radius in miles. Default 5, max 25.
`x_payment`	No	Optional. A signed x402 protocol payment payload (base64), used instead of an API key to pay for ONE address-level pull in USDC on Base network. If addresses=true and neither an API key nor x_payment is provided, the response is an HTTP 402 with full payment instructions (pay_to address, amount, network) an agent can act on to construct this payload and retry.
`hours_ahead`	No	dataset=weather only (Model-Based Hourly Forecast by Address). Forecast 0-48h out instead of current conditions -- snaps to the nearest available forecast hour, response's forecast_hour_used says exactly what you got.
`date_of_loss`	No	dataset=history only. YYYY-MM-DD. Anchors the report around this date -- returns the real weather events recorded on and immediately around that date, for reference. Not a determination of whether any claim is valid.
`max_severity`	No	Maximum measured severity.
`min_severity`	No	Minimum measured severity (e.g. 1.5 = 1.5 inch hail). Check severity_by_type in a preview for the real unit.

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 4, 2026

changedInput schema / properties / details / description

Previous value: -"dataset=weather only. true = full current-conditions pull, billed $0.0002/call. false (default) = free lean response, no account needed. Equivalent to addresses=true for this dataset."New value: +"dataset=weather only (Model-Based Weather by Address). true = full current-conditions pull, billed $0.0002/call. false (default) = free lean response, no account needed. Equivalent to addresses=true for this dataset."

changedInput schema / properties / hours_ahead / description

Previous value: -"dataset=weather only. Forecast 0-48h out instead of current conditions -- snaps to the nearest available forecast hour, response's forecast_hour_used says exactly what you got."New value: +"dataset=weather only (Model-Based Hourly Forecast by Address). Forecast 0-48h out instead of current conditions -- snaps to the nearest available forecast hour, response's forecast_hour_used says exactly what you got."

changedInput schema / properties / radius_mi / description

Previous value: -"dataset=history or dataset=weather only. Search radius in miles. Default 5, max 25."New value: +"dataset=history only. Search radius in miles. Default 5, max 25."

Changed2 schema fields changedOct 4, 2026

changedInput schema / properties / details / description

Previous value: -"dataset=weather only. true = full 164-field pull, billed $0.0002/call. false (default) = free 10-field lean response, no account needed. Equivalent to addresses=true for this dataset."New value: +"dataset=weather only. true = full current-conditions pull, billed $0.0002/call. false (default) = free lean response, no account needed. Equivalent to addresses=true for this dataset."

changedInput schema / properties / hours_ahead / description

Previous value: -"dataset=weather only. Real HRRR forecast 0-48h out instead of current conditions -- snaps to the nearest real available forecast hour, response's forecast_hour_used says exactly what you got."New value: +"dataset=weather only. Forecast 0-48h out instead of current conditions -- snaps to the nearest available forecast hour, response's forecast_hour_used says exactly what you got."

Changed1 schema field changedSep 28, 2026

changedInput schema / properties / date_of_loss / description

Previous value: -"dataset=history only. YYYY-MM-DD. Anchors the report around this date -- returns a real yes/no on whether weather data supports a loss that day, plus real events immediately before and after it."New value: +"dataset=history only. YYYY-MM-DD. Anchors the report around this date -- returns the real weather events recorded on and immediately around that date, for reference. Not a determination of whether any claim is valid."

Changed1 schema field changedSep 26, 2026

addedInput schema / properties / hours_ahead

Added value: +{
+  "description": "dataset=weather only. Real HRRR forecast 0-48h out instead of current conditions -- snaps to the nearest real available forecast hour, response's forecast_hour_used says exactly what you got.",
+  "maximum": 48,
+  "minimum": 0,
+  "type": "integer"
+}

Changed1 schema field changedSep 26, 2026

changedInput schema / properties / window / enum

Previous value: -[
-  "24h",
-  "48h",
-  "3d",
-  "5d",
-  "7d",
-  "10d",
-  "16d"
-]New value: +[
+  "24h",
+  "48h",
+  "3d",
+  "5d",
+  "7d",
+  "10d"
+]

Changed1 schema field changedSep 26, 2026

changedInput schema / properties / dataset / enum

Previous value: -[
-  "storms",
-  "risk",
-  "address",
-  "coverage",
-  "facilities",
-  "wildfire",
-  "at_risk",
-  "daily",
-  "history",
-  "weather"
-]New value: +[
+  "storms",
+  "risk",
+  "address",
+  "coverage",
+  "facilities",
+  "wildfire",
+  "at_risk",
+  "daily",
+  "history",
+  "weather",
+  "hazard_score"
+]

Changed9 schema fields changedSep 26, 2026

addedInput schema / properties / category

Added value: +{
+  "description": "dataset=facilities only. Facility category filter.",
+  "type": "string"
+}

addedInput schema / properties / date_of_loss

Added value: +{
+  "description": "dataset=history only. YYYY-MM-DD. Anchors the report around this date -- returns a real yes/no on whether weather data supports a loss that day, plus real events immediately before and after it.",
+  "type": "string"
+}

addedInput schema / properties / details

Added value: +{
+  "default": false,
+  "description": "dataset=weather only. true = full 164-field pull, billed $0.0002/call. false (default) = free 10-field lean response, no account needed. Equivalent to addresses=true for this dataset.",
+  "type": "boolean"
+}

addedInput schema / properties / kind

Added value: +{
+  "description": "dataset=at_risk only. Narrows to 'schools' or 'businesses'.",
+  "type": "string"
+}

addedInput schema / properties / limit

Added value: +{
+  "description": "Max records on the real paid pull (default 2000, real per-dataset caps still apply -- e.g. storms caps at 5000).",
+  "type": "integer"
+}

addedInput schema / properties / months

Added value: +{
+  "description": "dataset=storms only. Returns month-bucketed history totals instead of individual leads, for the last N months.",
+  "type": "integer"
+}

changedInput schema / properties / peril / description

Previous value: -"Storm type filter (dataset=storms only). Use the exact names returned under storm_types in a free preview for that county, e.g. HAIL, THUNDERSTORM_WIND, FLASH_FLOOD, HEAVY_RAIN, FLOOD, TORNADO."New value: +"Storm/risk type filter. Used by dataset=storms and dataset=risk (narrows to one storm type -- use the exact names returned under storm_types in a free preview) and by dataset=at_risk (narrows to one peril bucket, a different real meaning -- check that dataset's own preview for its real values). Common storms/risk values: HAIL, THUNDERSTORM_WIND, FLASH_FLOOD, HEAVY_RAIN, FLOOD, TORNADO."

addedInput schema / properties / radius_mi

Added value: +{
+  "description": "dataset=history or dataset=weather only. Search radius in miles. Default 5, max 25.",
+  "type": "number"
+}

addedInput schema / properties / window

Added value: +{
+  "description": "dataset=risk only. Forecast window. Default 24h.",
+  "enum": [
+    "24h",
+    "48h",
+    "3d",
+    "5d",
+    "7d",
+    "10d",
+    "16d"
+  ],
+  "type": "string"
+}

Changed1 schema field changedSep 26, 2026

changedInput schema / properties / dataset / enum

Previous value: -[
-  "storms",
-  "risk",
-  "address",
-  "coverage",
-  "facilities",
-  "wildfire",
-  "at_risk",
-  "daily"
-]New value: +[
+  "storms",
+  "risk",
+  "address",
+  "coverage",
+  "facilities",
+  "wildfire",
+  "at_risk",
+  "daily",
+  "history",
+  "weather"
+]

AddedSep 25, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Annotations cover only readOnlyHint and openWorldHint. The description adds the behavior that actually matters: free preview vs paid pull, the requirement for the user's own API key or an x402 USDC payment, the HTTP 402 fallback with pay_to/amount/network, and per-call billing. It also discloses a hard operational rule for the no-argument case.

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?

Long but front-loaded: routing guidance and the sibling exclusion list come first, then the dataset enumeration, then payment behavior, then the no-argument rule. The parenthetical parameter list is dense, but nearly every clause carries routing or billing information an agent needs.

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?

There is no output schema, and the description compensates by describing the free-preview vs paid return semantics, the HTTP 402 error shape, and fields like forecast_hour_used. It stops short of describing the structure of the dataset payloads themselves, which for a spillover tool of this breadth is a real but acceptable gap.

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 the schema already documents all 23 parameters (e.g. window, months, date_of_loss, radius_mi). The description reinforces which parameters the dedicated tools do not expose and repeats the addresses/details free-vs-paid semantics, but adds little beyond the schema. Baseline 3 applies.

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?

The description states a specific verb+resource and scope immediately: it is a 'CATCH-ALL and PAID-PULL tool' for Atlas United data across all datasets. It names all five siblings and the exact conditions under which this tool (not them) applies, so an agent can route without opening any schema.

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

Usage Guidelines5/5

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

Explicit when-to-use and when-not-to-use: 'Prefer the dedicated tools below when one fits' with a per-sibling scope (one county / one address / past 365 days, etc.), followed by an enumerated 'Use THIS tool for:' list. This is textbook routing guidance with named alternatives.

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

All TrueFixR Storm Data API 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.

Atlas United data, all datasets (advanced / multi-county)

Input Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources