Skip to main content
Glama
cliwant

mcp-sam-gov

by cliwant

fema_disaster_declarations

Read-only

Retrieve FEMA disaster declarations filtered by state, incident type, declaration type, fiscal year, or date range. Uses the keyless OpenFEMA DisasterDeclarationsSummaries dataset.

Instructions

Look up FEMA disaster / emergency declarations by state, type, incident, year, or date (keyless OpenFEMA, dataset DisasterDeclarationsSummaries v2, ~70k rows). Structured filters (module-built into an OData $filter; each LIVE-VERIFIED to narrow): state (→ state), incidentType (e.g. 'Flood'), declarationType (DR/EM/FM), fyDeclared, disasterNumber, declaredDateFrom/declaredDateTo (declarationDate ge/le), paProgramDeclared/iaProgramDeclared (booleans). limit (≤1000, def 100 → $top), offset (→ $skip). HONESTY: the module ALWAYS sends $inlinecount=allpages so totalAvailable is the EXACT filtered total (metadata.count), never the page length; genuine-empty ⇒ complete:true/total:0; an outage/400/404 THROWS (never a fake empty). NOTE: per-dataset OData field names differ — 'state' here is the real field, whereas the public-assistance tool maps 'state' to 'stateAbbreviation'.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoRows per page ($top), 1..1000, default 100.
stateNoFilter by state (→ state eq 'XX'). 2-letter code.
offsetNo0-based row offset ($skip) for pagination, default 0.
fyDeclaredNoFilter by fiscal year declared (→ fyDeclared eq N). e.g. 2024.
incidentTypeNoFilter by incident type (→ incidentType eq '...'). e.g. 'Flood', 'Hurricane', 'Winter Storm'.
declaredDateToNoLatest declaration date, inclusive (→ declarationDate le 'ISO').
disasterNumberNoFilter by FEMA disaster number (→ disasterNumber eq N).
declarationTypeNoFilter by declaration type (→ declarationType eq 'XX'): DR (major disaster), EM (emergency), FM (fire management).
declaredDateFromNoEarliest declaration date, inclusive (→ declarationDate ge 'ISO').
iaProgramDeclaredNoFilter to declarations where the Individual Assistance program was declared (→ iaProgramDeclared eq true/false).
paProgramDeclaredNoFilter to declarations where the Public Assistance program was declared (→ paProgramDeclared eq true/false).
Behavior5/5

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

Beyond the readOnlyHint and openWorldHint annotations, the description details the OData query mechanics (always sends $inlinecount=allpages), the meaning of totalAvailable, and genuine empty vs. error handling. It also explains how filters are built and verified.

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 description is detailed but well-organized, with sections for filters, pagination, honesty notes, and field-name caveats. It is longer than ideal, but every sentence adds value.

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?

Given 11 parameters, no required fields, and no output schema, the description covers the data source, filter construction, pagination, error handling, and field name nuances. It is comprehensive for an API tool.

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 100% schema coverage, baseline is 3. The description adds value by explaining the OData filter syntax for each parameter, noting the real field names, and comparing to other tools. It clarifies the meaning of date parameters and boolean filters.

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 clearly states the tool looks up FEMA disaster/emergency declarations by various filters such as state, type, incident, year, or date. It distinguishes itself from sibling tools like fema_search_public_assistance by noting field name differences, and from fema_search_hazard_mitigation by focusing on declarations.

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 context by noting that the state field matches the real field in the dataset, contrasting with other tools. It also mentions the dataset size and filter construction, but does not explicitly state when to use this tool over alternatives.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/cliwant/mcp-sam-gov'

If you have feedback or need assistance with the MCP directory API, please join our Discord server