FEMA Disasters

get_disaster_declarations

Get FEMA disaster declarations filtered by state, year, or type.

Returns federal disaster declarations including major disasters,
emergencies, and fire management assistance. Each record includes
the disaster number, title, declaration date, and affected area.

Args:
    state: Two-letter US state abbreviation (e.g. 'CA', 'TX', 'FL').
    year: Filter by fiscal year of the declaration (e.g. 2023).
    disaster_type: Declaration type code: 'DR' (major disaster),
        'EM' (emergency), or 'FM' (fire management assistance).
    limit: Maximum number of records to return (default 25, max 1000).

Input Schema

TableJSON Schema

Name	Required	Description	Default
`year`	No
`limit`	No
`state`	No
`disaster_type`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedApr 3, 2026

TDQS

A4.6/5.0

Behavior4/5

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

With no annotations, the description carries the burden. It explains the read-only nature via 'Get' and includes behavioral details such as the default and maximum limit. It also specifies the type of records returned, but does not mention authentication, pagination, or error conditions, which would make it more transparent.

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?

The description is concise and well-structured: a one-line summary, a brief explanatory paragraph, and a clear Args list. Every sentence provides necessary information without waste.

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?

The description covers the tool's purpose, all parameter semantics, and record contents. Given the output schema exists, return format is already available. This is sufficiently complete for an agent to select and invoke the tool correctly, even without explicit alternative tool guidance.

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

Parameters5/5

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

Schema description coverage is 0%, yet the description thoroughly documents each parameter with examples and accepted values (e.g., state abbreviations, disaster_type codes, limit range). This fully compensates for the schema's lack of descriptions.

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 opens with 'Get FEMA disaster declarations filtered by state, year, or type,' clearly identifying the operation and resource. It also specifies it returns major disasters, emergencies, and fire management assistance, distinguishing it from sibling tools like get_disaster_detail or grants.

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?

The description provides clear context that this tool returns a filtered list of declarations, and explains the available filters. However, it does not explicitly mention when to prefer this over sibling tools or any exclusions, though the scope is implied by the listing nature.

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

All FEMA Disasters 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?