fema-mcp-server

Get FEMA Public Assistance Projects

fema_get_public_assistance

Read-only

Retrieve Public Assistance (PA) funded project records for a disaster or state — shows where federal recovery money was obligated. Returns applicant, damage category, project size and status, federal share obligated, and total obligated amounts. Either disaster_number or state must be provided. Use disaster_number (from fema_search_disasters) to scope to a single declaration, or state to browse all PA projects for a state. PA projects are created only when the PA program is declared (pa_declared: true on the disaster).

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No	Maximum number of projects to return (1–1000, default 100).
`state`	No	Two-letter state code to browse all PA projects for a state.
`county`	No	Filter by county name substring.
`offset`	No	Pagination offset (default 0).
`disaster_number`	No	FEMA disaster number to scope results to a single declaration. Numbers above 32767 match no declaration.

Output Schema

TableJSON Schema

Name	Required	Description
`error`	No	Present when the call failed. Absent on success.
`notice`	No	Paging guidance when offset is at or past the end of the matching projects — names the total and the last valid offset.
`projects`	No	Public assistance funded project records.
`totalCount`	No	Total matching projects before pagination — exceeds returned_count when results were capped at the limit.
`total_count`	No	Total matching projects before pagination.
`returned_count`	No	Number of projects in this response.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedSep 24, 2026

changedOutput schema / properties / projects / items / properties / federal_share_obligated / description

Previous value: -"Federal dollars obligated for this project in USD. Absent before obligation."New value: +"Federal dollars obligated for this project in USD; 0 when nothing is obligated."

changedOutput schema / properties / projects / items / properties / total_obligated / description

Previous value: -"Total obligated amount across all funding sources in USD. Absent before obligation."New value: +"Total obligated amount across all funding sources in USD; 0 when nothing is obligated."

Changed4 schema fields changedSep 24, 2026

changedInput schema / properties / disaster_number / description

Previous value: -"FEMA disaster number to scope results to a single declaration."New value: +"FEMA disaster number to scope results to a single declaration. Numbers above 32767 match no declaration."

changedOutput schema / properties / error / properties / data / properties / reason / description

Previous value: -"Machine-readable failure mode. Declared by this tool: `invalid_state`: The state parameter is not a valid 2-letter US state/territory code. `missing_filter`: Neither disaster_number nor state was provided. `no_results`: No PA project records found for the given filters. Other values are possible when a failure originates below the handler."New value: +"Machine-readable failure mode. Declared by this tool: `invalid_state`: The state parameter is not a valid 2-letter US state/territory code. `missing_filter`: Neither disaster_number nor state was provided. `not_found`: The disaster number is above 32767, the highest number OpenFEMA holds, so no declaration exists. `no_results`: No PA project records found for the given filters. Other values are possible when a failure originates below the handler."

changedOutput schema / properties / error / properties / data / properties / reason / examples

Previous value: -[
-  "invalid_state",
-  "missing_filter",
-  "no_results"
-]New value: +[
+  "invalid_state",
+  "missing_filter",
+  "not_found",
+  "no_results"
+]

changedOutput schema / properties / notice / description

Previous value: -"Guidance when no results were found."New value: +"Paging guidance when offset is at or past the end of the matching projects — names the total and the last valid offset."

Changed6 schema fields changedAug 24, 2026

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

addedInput schema / additionalProperties
```
Added value: +false
```

changedOutput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

addedOutput schema / anyOf

Added value: +[
+  {
+    "not": {
+      "required": [
+        "error"
+      ]
+    },
+    "required": [
+      "projects",
+      "total_count",
+      "returned_count"
+    ]
+  },
+  {
+    "required": [
+      "error"
+    ]
+  }
+]

addedOutput schema / properties / error

Added value: +{
+  "additionalProperties": {},
+  "description": "Present when the call failed. Absent on success.",
+  "properties": {
+    "code": {
+      "description": "JSON-RPC error code for this failure.",
+      "maximum": 9007199254740991,
+      "minimum": -9007199254740991,
+      "type": "integer"
+    },
+    "data": {
+      "additionalProperties": {},
+      "properties": {
+        "reason": {
+          "description": "Machine-readable failure mode. Declared by this tool: `invalid_state`: The state parameter is not a valid 2-letter US state/territory code. `missing_filter`: Neither disaster_number nor state was provided. `no_results`: No PA project records found for the given filters. Other values are possible when a failure originates below the handler.",
+          "examples": [
+            "invalid_state",
+            "missing_filter",
+            "no_results"
+          ],
+          "type": "string"
+        },
+        "recovery": {
+          "additionalProperties": {},
+          "description": "Actionable next step for the caller.",
+          "properties": {
+            "hint": {
+              "type": "string"
+            }
+          },
+          "required": [
+            "hint"
+          ],
+          "type": "object"
+        },
+        "retryable": {
+          "description": "Whether retrying may succeed.",
+          "type": "boolean"
+        }
+      },
+      "type": "object"
+    },
+    "message": {
+      "description": "Human-readable description of what went wrong.",
+      "type": "string"
+    }
+  },
+  "required": [
+    "code",
+    "message"
+  ],
+  "type": "object"
+}

removedOutput schema / required

Removed value: -[
-  "projects",
-  "total_count",
-  "returned_count"
-]

Changed1 schema field changedJun 12, 2026

addedOutput schema / properties / totalCount

Added value: +{
+  "description": "Total matching projects before pagination — exceeds returned_count when results were capped at the limit.",
+  "type": "number"
+}

First observedJun 7, 2026

TDQS

A4.7/5.0

Behavior4/5

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

Annotations already mark the tool as read-only and open-world. The description adds useful behavioral context beyond that: PA projects only exist when the PA program was declared, and there is a mandatory but not schema-enforced one-of constraint. It does not contradict the annotations.

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 three sentences long and front-loads the core action, then lists return contents, then gives usage rules. Every sentence earns its place, and there is no filler or redundancy with the schema.

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 output schema exists and annotations cover read-only/open-world behavior, the description supplies the missing selection context: filters, prerequisites, and how to scope queries. An agent has enough information to invoke this tool correctly without further inference.

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?

The schema already documents all five parameters with 100% coverage, so the baseline is 3. The description adds value by clarifying the mutual-exclusion relationship between disaster_number and state, and by telling the agent where to get disaster_number from, which is not in 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 retrieves Public Assistance funded project records for a disaster or state, and enumerates the key data returned. It is distinct from sibling tools like fema_get_housing_assistance and fema_search_disasters, and the title is expanded with meaningful detail.

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?

It explicitly states the either/or requirement: disaster_number or state must be provided, and explains when to prefer each. It also references fema_search_disasters as the source for disaster_number and notes the pa_declared prerequisite, giving concrete selection guidance.

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

All fema-mcp-server 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.