Skip to main content
Glama
cliwant

mcp-sam-gov

by cliwant

fema_search_public_assistance

Read-only

Search FEMA Public Assistance funded projects using filters like state, disaster number, amount, and date. Get exact totals and paginated results from the OpenFEMA dataset.

Instructions

Search FEMA Public Assistance funded projects — federal emergency-assistance spend to state/local/tribal applicants (keyless OpenFEMA, dataset PublicAssistanceFundedProjectsDetails v2, ~800k rows). Structured filters (module-built into an OData $filter; each LIVE-VERIFIED to narrow): state (→ stateAbbreviation), disasterNumber, applicantId, damageCategoryCode (e.g. 'B' = Emergency Protective Measures), incidentType, minProjectAmount/maxProjectAmount (projectAmount ge/le), declaredDateFrom/declaredDateTo (declarationDate 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 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).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoRows per page ($top), 1..1000, default 100.
stateNoFilter by applicant state (→ stateAbbreviation eq 'XX'). 2-letter code.
offsetNo0-based row offset ($skip) for pagination, default 0.
applicantIdNoFilter by applicant id (→ applicantId eq '...'). e.g. '015-UF5E0-00'.
incidentTypeNoFilter by incident type (→ incidentType eq '...'). e.g. 'Flood', 'Hurricane', 'Severe Storm'.
declaredDateToNoLatest declaration date, inclusive (→ declarationDate le 'ISO').
disasterNumberNoFilter by FEMA disaster number (→ disasterNumber eq N).
declaredDateFromNoEarliest declaration date, inclusive (→ declarationDate ge 'ISO').
maxProjectAmountNoMaximum project amount (→ projectAmount le N).
minProjectAmountNoMinimum project amount (→ projectAmount ge N).
damageCategoryCodeNoFilter by PA damage category code (→ damageCategoryCode eq 'X'). e.g. 'B' = Emergency Protective Measures, 'C'–'G' = permanent work.
Behavior5/5

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

The description goes far beyond annotations by disclosing inlinecount behavior, exact total count, null handling, empty response format, and error throwing. It also notes filters are 'LIVE-VERIFIED', adding reliability context.

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 dense but well-structured with a clear logical flow: purpose, filters, honesty notes. Some redundancy could be trimmed, 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 the complexity (11 parameters, no output schema), the description covers behavioral details, edge cases, authenticity, and error handling. It provides enough context for effective use without an output schema.

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?

Even though schema coverage is 100%, the description adds significant meaning: mapping filters to OData fields, providing example values, explaining limit/offset in API terms, and indicating filters are module-built. This enriches understanding beyond the schema.

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 searches FEMA Public Assistance funded projects, specifies the exact dataset and version, and distinguishes it from sibling tools like fema_disaster_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 clear context on when to use the tool (searching PA projects) and details the structured filters. It implies alternatives exist (e.g., disaster declarations) but doesn't explicitly state when not to use it.

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