How to Use FEMA disaster declarations in Amp
Returns disaster declaration summaries with designated areas, incident information, and declared assistance programs. Use it to find declarations for a place or period, or inspect the areas attached to a disaster number.
Prompts to try with FEMA disaster declarations in Amp
Copy an example into Amp, or ask in your own words.
Use FEMA disaster declarations to collect Texas declarations from January 1 through December 31, 2024, and add a report to this project comparing distinct disaster numbers with designated-area row counts.
Use FEMA disaster declarations to look this up and give me the result as a table. Save the result in ./assets.
Pull the latest numbers from FEMA disaster declarations and tell me what changed since last week.
Check FEMA disaster declarations and summarize what you find in three bullet points.
Pull the newest data from FEMA disaster declarations and give me the result as a table.
How to set up FEMA disaster declarations in Amp
Pick the way that suits you. Each takes about two minutes.
Use Spiral's MCP server
- Add the server
No header and no client ID or secret: Amp registers itself with Spiral.
amp mcp add spiral https://api.spiral.ai/mcp
- Sign in
Start amp. Amp opens Spiral's sign-in page in your browser: sign in, pick the organization and click Authorize. No API key.
- Check it
amp mcp doctor
Use the Spiral skill
- Send Amp this message
Your agent reads Spiral's skill and sets itself up.
set up https://spiral.ai/SKILL.md
- Sign in or paste a key
Approve Spiral in the browser, or give the agent a key from the console.
Use the Spiral CLI
- Install and sign in
Installs the Spiral CLI, signs you in and adds its skill to your coding agents.
npx -y spiral-cli@latest init
Call the Spiral API
- Create an API key
In the console, under API keys.
- Run FEMA disaster declarations
One request; the result comes back by polling or a webhook.
curl https://api.spiral.ai/v1/runs \ -H "Authorization: Bearer $SPIRAL_API_KEY" \ -H "Content-Type: application/json" \ -H "Idempotency-Key: $(uuidgen)" \ -d '{ "provider": "alexandria", "model": "fema-gov/us-disaster-assistance/search_disaster_declarations", "input": { "skip": 0 } }'
Then paste one of the prompts above: Amp finds FEMA disaster declarations on Spiral, shows the price and runs it.
FEMA disaster declarations providers and prices
Spiral runs FEMA disaster declarations through Alexandria. Open a card for today's price, with every fee included.
Settings you can ask for
Ask Amp for any of these in your prompt.
| Setting | Allowed values | Default | Description |
|---|---|---|---|
| Skip | a number from 0 | 0 | Rows to skip (OpenFEMA $skip); pass the previous page's |
| Limit | 1 to 1000 | 100 | Rows per page (OpenFEMA $top). |
| Disaster number | 1 to 32767 | FEMA disaster number (e.g. 4931); returns that disaster's designated-area rows. |
Every API field of FEMA · Search disaster declarations is on its tool page: open its card above.
What can you do with FEMA disaster declarations in Amp?
Build a county disaster-history report that keeps designated areas separate from distinct declarations. Add collection updates and publication checks so the project's FEMA evidence can be refreshed when its source data changes.
County mitigation plan evidence
Build a declaration history for Harris County, Texas, inspect the records behind selected events, and add relevant OpenFEMA program data. Maintain the collection through updates and check dataset and National Risk Index publication status before revising the plan's evidence.
Public disaster-history dashboard
Create a dashboard of declared events and designated areas for Florida. Collect the historical records, inspect selected rows, incorporate focused program queries, and maintain revisions; show publication checks alongside any separately maintained National Risk Index analysis.
Regional business continuity review
Prepare a review of declared disasters affecting business locations in Texas and Louisiana. Use historical collections, focused searches, record inspection, and program queries to document the events, then check record revisions and publication changes before the next review.
Maintain a disaster research collection
Maintain a research collection comparing California declaration history with selected OpenFEMA program records. Collect a baseline, inspect individual observations, apply supported updates, and track dataset and National Risk Index publication changes that could require rerunning the analysis.
Check a declaration-area claim
Investigate which areas a particular disaster declaration includes. Search by disaster number, retrieve the selected records, and compare their designated areas before citing them in a report.
Compare declaration history across states
Compare declared events in Texas, Louisiana, and Florida over a defined period. Collect every page and count distinct disaster numbers so declarations with more designated areas do not inflate the comparison.
More on FEMA disaster declarations and Amp
Overview
FEMA disaster declarations in other agents
Questions about FEMA disaster declarations in Amp
Can Amp use FEMA disaster declarations?
Yes. Add Spiral to Amp as an MCP server, and Amp can find and run FEMA disaster declarations like any built-in tool.
How much does FEMA disaster declarations cost in Amp?
$0.00873 per call. You pay from your Spiral balance as you go, with no subscription, and a failed run is not charged. Your Amp plan is separate.
Do I need an Alexandria account to use FEMA disaster declarations in Amp?
No. Spiral runs FEMA disaster declarations on its own Alexandria account. You sign in to Spiral once and never paste a key.
How long does it take to set up FEMA disaster declarations in Amp?
About two minutes: add the server, then sign in, then check it.
Does Amp wait while FEMA disaster declarations runs?
FEMA disaster declarations runs in the background. Amp starts the run, checks on it and gives you the json when it's ready.
How far back does FEMA's disaster history go?
The declaration history starts in 1953. County information is unavailable before 1964, and FEMA describes historical Fire Management records as partial.
Does one declaration record equal one disaster?
No. Disaster Declarations Summaries is organized at the county level, so one disaster can appear in multiple records. Count distinct disaster numbers to count declarations.
What geographic detail does the National Risk Index provide?
The National Risk Index provides a baseline relative risk measurement for counties and Census tracts across 18 natural hazards. It describes community risk rather than an individual property's assessment.
Does every OpenFEMA dataset follow the same update schedule?
OpenFEMA publishes update frequency separately for each dataset. Its dataset metadata also identifies versions and deprecation status, so freshness should be checked against the particular dataset being analyzed.
Can previously published FEMA records change?
Yes. FEMA's official collection example checks whether a dataset has refreshed and then retrieves new or refreshed records. A declaration-history collection therefore needs to account for revisions as well as additions.
Start using FEMA disaster declarations in Amp
One Spiral account for every tool your agent needs. No subscription; you pay per run.
Paste this into Amp:
set up https://spiral.ai/SKILL.md


