Skip to main content
Glama

Get FEMA Public Assistance Projects

fema_get_public_assistance
Read-only

Retrieve Public Assistance (PA) funded project records, including recipient name, damage category, project status, and federal obligations. Supply disaster_number from fema_search_disasters or a state code. A page holds up to 100,000 characters of projects. Use next_offset to continue. With DataCanvas enabled, an overflowing first page also stages up to 50,000 matching rows for fema_dataframe_query.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "fema_get_public_assistance"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of projects to return (1–10000, default 100). A page also stops at 100,000 characters of projects (roughly 220 projects); when either bound leaves matching projects out, next_offset names the offset to continue from.
stateNoTwo-letter state code to browse all PA projects for a state.
countyNoFilter by county name (e.g., Harris, dekalb). Case-insensitive substring match: harris also matches Harrison. Recognized terminal County, Parish, Borough, and Census Area names accept plain or parenthesized types; unknown names retain original case fallbacks.
offsetNoPagination offset (default 0). Pass the previous page’s next_offset to continue.
canvas_idNoReuse a canvas returned by an earlier call. Used only when staging from offset 0; omit to stage on a new canvas.
disaster_numberNoFEMA disaster number to scope results to a single declaration. Numbers above 32767 match no declaration.

Output Schema

NameRequiredDescriptionDefault
errorNoPresent when the call failed. Absent on success.
noticeNoGuidance on missing matches, inline continuation, incomplete applicant names, or DataCanvas staging.
spilledNoWhether the filtered match was staged on a DataCanvas.
projectsNoPublic assistance funded project records from offset onward, bounded by limit and by 100,000 characters of projects.
canvas_idNoCanvas ID for querying the staged projects. Present after successful staging.
totalCountNoTotal matching projects before pagination — exceeds returned_count when results were capped at the limit.
next_offsetNoOffset of the next page: offset plus returned_count. Present only while matching projects remain past this page; pass it as offset to continue.
total_countNoTotal matching projects before pagination.
canvas_tablesNoStaged table metadata. Present after successful staging.
returned_countNoNumber of projects in this response.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed14 schema fields changed
    • addedInput schema / properties / canvas_id
      Added value: +{
      +  "description": "Reuse a canvas returned by an earlier call. Used only when staging from offset 0; omit to stage on a new canvas.",
      +  "pattern": "^[A-Za-z0-9_-]{10}$",
      +  "type": "string"
      +}
    • changedOutput schema / anyOf
      Previous value: -[
      -  {
      -    "not": {
      -      "required": [
      -        "error"
      -      ]
      -    },
      -    "required": [
      -      "projects",
      -      "total_count",
      -      "returned_count"
      -    ]
      -  },
      -  {
      -    "required": [
      -      "error"
      -    ]
      -  }
      -]New value: +[
      +  {
      +    "not": {
      +      "required": [
      +        "error"
      +      ]
      +    },
      +    "required": [
      +      "projects",
      +      "total_count",
      +      "returned_count",
      +      "spilled"
      +    ]
      +  },
      +  {
      +    "required": [
      +      "error"
      +    ]
      +  }
      +]
    • addedOutput schema / properties / canvas_id
      Added value: +{
      +  "description": "Canvas ID for querying the staged projects. Present after successful staging.",
      +  "pattern": "^[A-Za-z0-9_-]{10}$",
      +  "type": "string"
      +}
    • addedOutput schema / properties / canvas_tables
      Added value: +{
      +  "description": "Staged table metadata. Present after successful staging.",
      +  "items": {
      +    "additionalProperties": false,
      +    "description": "One staged Public Assistance project table.",
      +    "properties": {
      +      "dataset": {
      +        "description": "OpenFEMA dataset in this table.",
      +        "enum": [
      +          "PublicAssistanceFundedProjectsDetails",
      +          "HousingAssistanceOwners",
      +          "HousingAssistanceRenters"
      +        ],
      +        "type": "string"
      +      },
      +      "staged_count": {
      +        "description": "Number of filtered records staged in this table.",
      +        "type": "number"
      +      },
      +      "table_name": {
      +        "description": "Table name for fema_dataframe_describe and SQL FROM clauses.",
      +        "type": "string"
      +      },
      +      "truncated": {
      +        "description": "True when this table holds the first 50,000 of more matching records.",
      +        "type": "boolean"
      +      }
      +    },
      +    "required": [
      +      "dataset",
      +      "table_name",
      +      "staged_count",
      +      "truncated"
      +    ],
      +    "type": "object"
      +  },
      +  "type": "array"
      +}
    • 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. `not_found`: The disaster number is above 32767, the highest number OpenFEMA holds, so no declaration exists. `request_too_long`: The county value makes the request URL longer than the roughly 8,900 characters OpenFEMA accepts. 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. `request_too_long`: The county value makes the request URL longer than the roughly 8,900 characters OpenFEMA accepts. `canvas_not_found`: The canvas supplied for PA staging is missing or expired. 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",
      -  "not_found",
      -  "request_too_long"
      -]New value: +[
      +  "invalid_state",
      +  "missing_filter",
      +  "not_found",
      +  "request_too_long",
      +  "canvas_not_found"
      +]
    • changedOutput schema / properties / notice / description
      Previous value: -"Zero-match guidance for supplied filters and declared programs, or paging guidance: the continuation offset and whether limit or the response budget ended the page, or the last valid offset for a nonzero total."New value: +"Guidance on missing matches, inline continuation, incomplete applicant names, or DataCanvas staging."
    • addedOutput schema / properties / projects / items / properties / applicant_name
      Added value: +{
      +  "description": "Recipient organization name from the applicant record for this disaster and applicant ID.",
      +  "type": "string"
      +}
    • changedOutput schema / properties / projects / items / properties / application_title / description
      Previous value: -"Name of the applicant organization or project. Absent when not recorded."New value: +"The application's free-form project title. Absent when not recorded."
    • addedOutput schema / properties / projects / items / properties / county_fips
      Added value: +{
      +  "description": "Five-digit county FIPS code, including leading zeros. Absent when either component is unavailable.",
      +  "type": "string"
      +}
    • addedOutput schema / properties / projects / items / properties / last_obligation_date
      Added value: +{
      +  "description": "ISO 8601 date the latest federal obligation was recorded. Absent before obligation.",
      +  "type": "string"
      +}
    • addedOutput schema / properties / projects / items / properties / mitigation_amount
      Added value: +{
      +  "description": "Proposed Section 406 mitigation amount in USD, including zero and negative adjustments.",
      +  "type": "number"
      +}
    • addedOutput schema / properties / projects / items / properties / project_process_step
      Added value: +{
      +  "description": "Current FEMA project workflow step. Absent when not recorded.",
      +  "type": "string"
      +}
    • addedOutput schema / properties / spilled
      Added value: +{
      +  "description": "Whether the filtered match was staged on a DataCanvas.",
      +  "type": "boolean"
      +}
  2. Changed1 schema field changed
    • changedInput schema / properties / county / description
      Previous value: -"Filter by county name (e.g., Harris, dekalb). Case-insensitive substring match: harris also matches Harrison."New value: +"Filter by county name (e.g., Harris, dekalb). Case-insensitive substring match: harris also matches Harrison. Recognized terminal County, Parish, Borough, and Census Area names accept plain or parenthesized types; unknown names retain original case fallbacks."
  3. Changed3 schema fields changed
    • 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. `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. `request_too_long`: The county value makes the request URL longer than the roughly 8,900 characters OpenFEMA accepts. 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. `request_too_long`: The county value makes the request URL longer than the roughly 8,900 characters OpenFEMA accepts. 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",
      -  "not_found",
      -  "no_results",
      -  "request_too_long"
      -]New value: +[
      +  "invalid_state",
      +  "missing_filter",
      +  "not_found",
      +  "request_too_long"
      +]
    • changedOutput schema / properties / notice / description
      Previous value: -"Paging guidance: the offset to continue from and whether limit or the response budget ended the page, or, when offset is at or past the end, the total and the last valid offset."New value: +"Zero-match guidance for supplied filters and declared programs, or paging guidance: the continuation offset and whether limit or the response budget ended the page, or the last valid offset for a nonzero total."
  4. Changed13 schema fields changed
    • changedInput schema / properties / county / description
      Previous value: -"Filter by county name substring."New value: +"Filter by county name (e.g., Harris, dekalb). Case-insensitive substring match: harris also matches Harrison."
    • changedInput schema / properties / limit / description
      Previous value: -"Maximum number of projects to return (1–1000, default 100)."New value: +"Maximum number of projects to return (1–10000, default 100). A page also stops at 100,000 characters of projects (roughly 220 projects); when either bound leaves matching projects out, next_offset names the offset to continue from."
    • changedInput schema / properties / limit / maximum
      Previous value: -1000New value: +10000
    • changedInput schema / properties / offset / description
      Previous value: -"Pagination offset (default 0)."New value: +"Pagination offset (default 0). Pass the previous page’s next_offset to continue."
    • 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. `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."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. `request_too_long`: The county value makes the request URL longer than the roughly 8,900 characters OpenFEMA accepts. 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",
      -  "not_found",
      -  "no_results"
      -]New value: +[
      +  "invalid_state",
      +  "missing_filter",
      +  "not_found",
      +  "no_results",
      +  "request_too_long"
      +]
    • addedOutput schema / properties / next_offset
      Added value: +{
      +  "description": "Offset of the next page: offset plus returned_count. Present only while matching projects remain past this page; pass it as offset to continue.",
      +  "type": "number"
      +}
    • changedOutput schema / properties / notice / description
      Previous value: -"Paging guidance when offset is at or past the end of the matching projects — names the total and the last valid offset."New value: +"Paging guidance: the offset to continue from and whether limit or the response budget ended the page, or, when offset is at or past the end, the total and the last valid offset."
    • changedOutput schema / properties / projects / description
      Previous value: -"Public assistance funded project records."New value: +"Public assistance funded project records from offset onward, bounded by limit and by 100,000 characters of projects."
    • changedOutput schema / properties / projects / items / properties / project_amount / description
      Previous value: -"Total estimated project cost in USD. Absent when not yet determined."New value: +"Estimated total eligible cost of the project in USD from FEMA's damage survey, without administrative costs. Absent when not yet determined."
    • changedOutput schema / properties / projects / items / properties / project_size / description
      Previous value: -"Project size classification: \"small\" (≤$1M) or \"large\" (>$1M). Absent when unclassified."New value: +"Large or Small, set by comparing the eligible amount from the damage survey with the large-project threshold FEMA sets for each fiscal year. Absent when unclassified."
    • changedOutput schema / properties / projects / items / properties / project_status / description
      Previous value: -"Current project status (e.g., Obligated, Closed, In Progress). Absent when not set."New value: +"Eligibility status of the project: Eligible (nearly all projects), Pending Eligibility Review, Ineligible, or Withdrawn. Absent when not set."
    • changedOutput schema / properties / projects / items / properties / total_obligated / description
      Previous value: -"Total obligated amount across all funding sources in USD; 0 when nothing is obligated."New value: +"Federal share of the eligible project amount plus State (recipient) and applicant (subrecipient) administrative costs, in USD; equals federal_share_obligated when no administrative costs are recorded. Holds no non-federal share. 0 when nothing is obligated."
  5. Changed2 schema fields changed
    • 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."
  6. Changed4 schema fields changed
    • 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."
  7. Changed6 schema fields changed
    • 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"
      -]
  8. Changed1 schema field changed
    • addedOutput schema / properties / totalCount
      Added value: +{
      +  "description": "Total matching projects before pagination — exceeds returned_count when results were capped at the limit.",
      +  "type": "number"
      +}
  9. First observed

TDQS

A4.2/5.0
Behavior5/5

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

With annotations only declaring readOnlyHint and openWorldHint, the description supplies the operational behavior the annotations cannot: the page cap of 100,000 characters (~220 projects), the limit bound, the next_offset continuation mechanism, and the DataCanvas side effect where an overflowing first page stages up to 50,000 rows for fema_dataframe_query. That staging side effect is exactly the kind of non-obvious behavior an agent needs before calling.

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?

Four sentences, front-loaded with purpose, then scoping inputs, then pagination, then the DataCanvas interaction, with no filler. 'A page holds up to 100,000 characters of projects' is slightly awkward phrasing but carries real information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema present, the description needn't explain return values, and annotations cover the read-only/open-world profile, so the remaining burden is pagination and side effects, which it covers well. The gap is the zero-required-parameter case: it never says what an unscoped call returns or how state and disaster_number interact when both are supplied.

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?

Schema description coverage is 100%, so the baseline is 3; the description earns more by adding meaning the schema lacks, namely where disaster_number comes from (fema_search_disasters) and that a state code is a substitute scoping route. Minor friction: it refers to 'next_offset' while the callable parameter is 'offset', a response-field/parameter name mismatch the schema only partially clarifies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb (Retrieve) and a precisely scoped resource (Public Assistance funded project records), then enumerates the returned fields (recipient name, damage category, project status, federal obligations). That program-level naming implicitly separates it from fema_get_housing_assistance, but no sibling is named explicitly, so it stops short of full differentiation.

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?

It tells the agent what to supply to scope results: disaster_number sourced from fema_search_disasters, or a state code as the browsing alternative. That is a clear routing instruction and a prerequisite chain to a sibling. It does not state exclusions or what happens when no scoping parameter is given, which is notable given zero required parameters.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.