How to Use NOAA annual storm records in Muse Code
Returns rows from one year’s event details, locations, or fatalities file. Use it to build county summaries, compare reported impacts, or collect records for local filtering.
Prompts to try with NOAA annual storm records in Muse Code
Copy an example into Muse Code, or ask in your own words.
Use NOAA annual storm records for 2023 to build a Florida event table in this project, with dates, event types, reported damage, and event IDs.
Use NOAA annual storm records for 2013 to create a map dataset of Oklahoma event location points, retaining event IDs for joins.
Use NOAA annual storm records to look this up and give me the result as a table. Save the result in ./assets.
Pull the latest numbers from NOAA annual storm records and tell me what changed since last week.
Check NOAA annual storm records and summarize what you find in three bullet points.
How to set up NOAA annual storm records in Muse Code
Pick the way that suits you. Each takes about two minutes.
Use Spiral's MCP server
- Install Muse Code
curl -fsSL https://dev.meta.ai/install.sh | bash
- Ask Muse to add the server
Start muse and ask:
Add the Spiral MCP server at https://api.spiral.ai/mcp
- Sign in
In your terminal, run:
muse mcp login spiral
Use the Spiral skill
- Send Muse Code 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 NOAA annual storm records
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": "ncei-noaa-gov/storm-events/records_list", "input": { "type": "details" } }'
Then paste one of the prompts above: Muse Code finds NOAA annual storm records on Spiral, shows the price and runs it.
NOAA annual storm records providers and prices
Spiral runs NOAA annual storm records through Alexandria. Open a card for today's price, with every fee included.
Settings you can ask for
Ask Muse Code for any of these in your prompt.
| Setting | Allowed values | Default | Description |
|---|---|---|---|
| Type | details, locations, or fatalities | Required without a cursor. | |
| Year | 1950 to 2100 | Data year (the | |
| Page size | 1 to 2000 | 2000 | Rows per page, at most 2000. |
Every API field of NOAA NCEI Storm Events Database bulk CSVs · Records list is on its tool page: open its card above.
What can you do with NOAA annual storm records in Muse Code?
Build a county storm-history report from NOAA's annual files and individual event records. A coding agent can add publication checks so the project's reports can be refreshed when NOAA changes a file.
County storm-history brief
Collect annual records for Harris County, Texas, examine selected events for narrative context, and check publication versions before refreshing the brief.
Historical event case study
Find records for the May 20, 2013, Moore, Oklahoma, tornado, examine the associated event details and location points, and identify the publication used for the study.
Reported damage comparison
Compare reported property and crop damage across years in Iowa, read the narratives behind selected events, and refresh calculations when NOAA revises the underlying files.
Storm location map
Build a map of published event points for Oklahoma in 2013, add event narratives to selected map entries, and check whether the source publications have changed.
Revision review
Detect a changed annual publication, compare its records with a saved copy, and inspect the details of events whose reported impacts changed.
Public storm archive
Create a searchable historical collection for Florida using annual records, event detail pages, and publication checks that identify when the collection needs refreshing.
More on NOAA annual storm records and Muse Code
Overview
NOAA annual storm records in other agents
Questions about NOAA annual storm records in Muse Code
Can Muse Code use NOAA annual storm records?
Yes. Add Spiral to Muse Code as an MCP server, and Muse Code can find and run NOAA annual storm records like any built-in tool.
How much does NOAA annual storm records cost in Muse Code?
$0.00873 per call. You pay from your Spiral balance as you go, with no subscription, and a failed run is not charged. Your Muse Code plan is separate.
Do I need an Alexandria account to use NOAA annual storm records in Muse Code?
No. Spiral runs NOAA annual storm records on its own Alexandria account. You sign in to Spiral once and never paste a key.
How long does it take to set up NOAA annual storm records in Muse Code?
About two minutes: install Muse Code, then ask Muse to add the server, then sign in.
Does Muse Code wait while NOAA annual storm records runs?
NOAA annual storm records runs in the background. Muse Code starts the run, checks on it and gives you the json when it's ready.
What geographic area does NOAA Storm Events cover?
It covers significant weather in the United States and adjacent water bodies. It is a regional storm archive, so it cannot supply a worldwide event history.
How far back do the records go?
The database begins in January 1950. That starting date describes the archive as a whole, rather than establishing complete coverage for every hazard throughout the period.
How soon do recent storms appear?
NOAA documents a delay of 75 to 90 days after the end of a data month. Its bulk-download documentation specifies monthly updates to the current yearly file and allows corrections to previous years.
Why are details, locations, and fatalities separate?
NOAA publishes three files linked by event ID. Details describe the event, locations provide indexed geographic points, and fatalities contain the associated fatality records.
How accurate are the reported impacts?
Property and crop damage are estimates. NOAA also cautions that outside reports may be unverified and that NWS does not guarantee the accuracy or validity of Storm Data.
Start using NOAA annual storm records in Muse Code
One Spiral account for every tool your agent needs. No subscription; you pay per run.
Paste this into Muse Code:
set up https://spiral.ai/SKILL.md


