Small Business Funding Finder

Disaster declarations and SBA help

disaster_help

Read-onlyIdempotent

Federal disaster declarations from the last 24 months for a state, or for one county, from FEMA's OpenFEMA Disaster Declarations Summaries. Each declaration has its FEMA number, title, incident type, declaration type (major disaster, emergency or fire management), declaration and incident dates, designated areas, the programs declared (Individual Assistance, Public Assistance, Hazard Mitigation), what that means for SBA disaster loans to a business under 13 CFR 123.3 and 123.4, and its FEMA disaster page. For a county it also lists bordering counties with a major disaster that included Individual Assistance, since economic injury loans can reach contiguous counties. Links SBA's disaster loan search, because SBA makes its own declarations that FEMA's data does not show. Cached for 6 hours. Informational, not legal advice.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "state": "<state>"
    },
    "name": "disaster_help"
  }
}

Input Schema

Name	Required	Description	Default
`state`	Yes	Two-letter code for a U.S. state, DC, Puerto Rico, the U.S. Virgin Islands, Guam, American Samoa or the Northern Mariana Islands, for example MT.
`county`	No	County, parish, borough or independent city, for example "Orange County" or "Orleans Parish". Leave out for the whole state.

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 3, 2026

TDQS

A4.2/5.0

Behavior4/5

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

The annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description still adds real context beyond them: the data source, a 6-hour cache, the county-level contiguous-county expansion, the SBA-declaration gap and an informational-not-legal-advice disclaimer. It stops short of describing error behavior or result limits.

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 front-loaded with source scope, then enumerates the returned fields, then adds caveats. It is dense but nearly every clause carries information. The 13 CFR citation is precise but adds weight an agent may not need.

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?

There is no output schema, so the description has to carry return shape, and it does — FEMA number, title, incident type, declaration type, dates, designated areas, declared programs, SBA implications and page link. Cache duration and the SBA data gap complete what an agent needs to call it and interpret the result.

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 coverage is 100%, so the baseline is 3. The description goes beyond the schema by explaining that supplying a county changes the output: it also lists bordering counties with a major disaster that included Individual Assistance, since economic injury loans can reach contiguous counties. That is genuine semantic value missing from 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 names a specific verb and resource — federal disaster declarations from FEMA's OpenFEMA Disaster Declarations Summaries — and bounds it to the last 24 months for a state or a single county. That is clearly distinct from the grant-search and loan siblings, so an agent can identify the tool without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It implies when to use the tool (looking up declarations for a state or county) and explains that SBA issues its own declarations not visible in FEMA data, pointing to SBA's loan search. But it never routes the agent explicitly to a sibling such as sba_loans or eligibility_explainer, and it states no when-not conditions.

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

All Small Business Funding Finder 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.

Resources

Need Help?