Skip to main content
Glama

US Flood Zone & Property Risk (FEMA, NOAA, USGS, Census)

Hazard History

hazard_history
Read-onlyIdempotent

Natural-hazard history for a US county or address: FEMA declarations (major disasters, emergencies and fire management, by type, with links), NOAA storm events with deaths and reported property damage by type and year, and USGS earthquakes within 100 km since 1950. One call, each source reported apart.

Three federal sources, fetched together:

  • FEMA declarations for the county since 1 January of the first year: the total (major disasters, emergencies and fire management), major disasters alone, count by incident type, and the declarations themselves with FEMA ids and links. Statewide declarations are included.

  • NOAA Storm Events for the county: events, deaths, injuries and reported property and crop damage (nominal dollars; unreported damage counts as 0, so it is a floor), by type and by year, plus the worst events. Events NOAA records for a forecast zone covering only this county (most heat and winter-storm deaths) count as the county's own; a zone covering several counties is counted, but its casualties and damage are reported apart in zone_based, because they are shared. The current year is incomplete; NOAA can trail by months.

  • USGS earthquakes of magnitude 2.5 or more within 100 km of the point since 1950: the count and the five largest. This needs a point, so it is skipped when only a county GEOID is given.

Each section has its own status; if one source is down the others still answer. If neither FEMA nor NOAA can answer, the call fails and is not charged. Connecticut's planning regions (since 2022) are not yet matched to the old counties FEMA and NOAA still use, so they are not answered; the old county GEOIDs (09001-09015) work. A GEOID that is not a county is not found. A geoid is used only when no address or coordinate is given.

When to use: Use for "has this area had floods, hurricanes or earthquakes", disaster declarations, storm damage history, or natural-hazard due diligence for a US property or county. For the flood zone at a property use flood_zone; for everything about an address in one call use address_profile.

Billed as property.hazard_history at 2c.

Every response includes a sources[] array naming the data origin and licence.

Input Schema

NameRequiredDescriptionDefault
latNo
lonNo
geoidNoFive-digit county GEOID, instead of a place (no earthquake section then).
yearsNoFull years back from 1 January, plus the current year so far.
addressNoA US street address.

Output Schema

NameRequiredDescriptionDefault
pointNo
yearsYes
countyYes
stormsYes
summaryYes
disastersYes
earthquakesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.8/5.0
Behavior5/5

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

Far beyond the annotations, it discloses per-section status, graceful degradation when one source is down, that the call fails and is not charged when both FEMA and NOAA fail, the 2c billing key, the Connecticut planning-region gap, NOAA's reporting lag, and that shared forecast zones are split into `zone_based`. It also clarifies that unreported damage is treated as a floor rather than a true zero.

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?

The one-line summary is front-loaded and the three bulleted source blocks make the length scannable rather than rambling. It is on the long side and repeats some scoping details (geoid/GEOID handling) in two places, but each section carries operational information.

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

Completeness5/5

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

For a multi-source aggregation tool the description covers input mutual exclusion, partial-failure semantics, edge cases (non-county GEOID, Connecticut regions), scoring/billing, and the sources[] provenance array. With an output schema present, no return-value documentation is needed.

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

Parameters4/5

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

With 60% schema coverage, the description usefully adds precedence rules the schema does not state: `geoid` is used only when no address or coordinate is supplied, and the earthquake section is skipped when only a GEOID is given. It also clarifies `years` as full years back from 1 January plus the current year, though lat/lon semantics (search radius) stay implicit.

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 opening sentence names the resource (natural-hazard history), the scope (US county or address) and the three concrete data sources (FEMA declarations, NOAA storm events, USGS earthquakes) with their filters. It is immediately distinguishable from siblings like flood_zone and address_profile, which are explicitly named later.

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?

An explicit 'When to use' block enumerates the triggering questions (floods/hurricanes/earthquakes, disaster declarations, storm damage history, due diligence) and names the two alternatives with the condition that selects each. Nothing about tool selection is left to inference.

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