Skip to main content
Glama
cliwant

mcp-sam-gov

by cliwant

fema_search_hazard_mitigation

Read-only

Search FEMA Hazard Mitigation Assistance disaster-resilience grants (HMGP, FMA, PDM, BRIC) — filter by state, program area, disaster number, amount, status. Uses OpenFEMA data.

Instructions

Search FEMA Hazard Mitigation Assistance projects — the disaster-RESILIENCE grant axis (HMGP/FMA/PDM/BRIC mitigation grants to state/local/tribal subrecipients, distinct from the disaster-RECOVERY spend in fema_search_public_assistance). Keyless OpenFEMA, dataset HazardMitigationAssistanceProjects v4, ~56k rows. Structured filters (module-built into an OData $filter; each LIVE-VERIFIED to narrow): state (→ state — the FULL state NAME, e.g. 'Alabama', NOT the 2-letter code), programArea (HMGP/FMA/PDM/BRIC/LPDM/FMA-SL), disasterNumber, status (e.g. 'Closed'), programFy, region (FEMA region 1–10), minProjectAmount/maxProjectAmount (projectAmount ge/le). 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; amount fields (projectAmount/federalShareObligated/initialObligationAmount/netValueBenefits) are number|null (a real 0 stays 0, absent → null); genuine-empty ⇒ complete:true/total:0; an outage/400/404 THROWS (never a fake empty). NOTE: 'state' here is the full name (this dataset 400s on a 2-letter code), whereas fema_search_public_assistance maps 'state' to the 2-letter 'stateAbbreviation'.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoRows per page ($top), 1..1000, default 100.
stateNoFilter by state (→ state eq '...'). Accepts EITHER a 2-letter code ('AL', like the other FEMA tools) OR the full name ('Alabama'); the module maps a 2-letter code to the full name this dataset requires.
offsetNo0-based row offset ($skip) for pagination, default 0.
regionNoFilter by FEMA region number 1–10 (→ region eq N).
statusNoFilter by project status (→ status eq '...'). e.g. 'Closed', 'Open'.
programFyNoFilter by program fiscal year (→ programFy eq N). e.g. 2005.
programAreaNoFilter by mitigation program (→ programArea eq '...'): HMGP (Hazard Mitigation Grant Program), FMA (Flood Mitigation Assistance), PDM (Pre-Disaster Mitigation), BRIC (Building Resilient Infrastructure and Communities), LPDM, FMA-SL.
disasterNumberNoFilter by FEMA disaster number (→ disasterNumber eq N).
maxProjectAmountNoMaximum project amount (→ projectAmount le N).
minProjectAmountNoMinimum project amount (→ projectAmount ge N).
Behavior4/5

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

Annotations already provide readOnlyHint and openWorldHint. Description adds honest details about $inlinecount behavior, null handling, and error throwing, which are beyond annotations.

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?

Well-structured with purpose, parameter details, and honesty section. Front-loaded but slightly verbose in spots; still efficient for the information provided.

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?

Covers all necessary aspects: pagination, filtering, error handling, output expectations. No output schema but description compensates fully.

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%, baseline 3. Description adds disambiguation for state vs sibling but introduces contradiction: says 'NOT the 2-letter code' while schema says it accepts both and maps. Slightly confusing.

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?

Clearly states verb 'Search', resource 'FEMA Hazard Mitigation Assistance projects', and explicitly distinguishes from sibling tool fema_search_public_assistance for disaster-recovery spend.

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?

Explicitly says when to use for disaster-resilience grants (HMGP/FMA/PDM/BRIC) and contrasts with recovery-focused sibling. Also notes state parameter difference from sibling.

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