Spiral gives your agent every tool with one account. Browse the tools →

Muse Code · Public Records

How to Use NOAA storm data publication status in Muse Code

Returns publication information for NOAA’s annual storm files, including file versions. Use it to identify changed publications before refreshing an analysis, including corrections to older years.

Prompts to try with NOAA storm data publication status in Muse Code

Copy an example into Muse Code, or ask in your own words.

Use NOAA storm data publication status for 2023 to add a publication-version check to this project's Florida storm report.

NOAA storm data publication statusMuse Code
Try asking
  • Use NOAA storm data publication status to look this up and give me the result as a table. Save the result in ./assets.

  • Pull the latest numbers from NOAA storm data publication status and tell me what changed since last week.

  • Check NOAA storm data publication status and summarize what you find in three bullet points.

  • Pull the newest data from NOAA storm data publication status and give me the result as a table.

How to set up NOAA storm data publication status in Muse Code

Pick the way that suits you. Each takes about two minutes.

Use Spiral's MCP server

  1. Install Muse Code
    curl -fsSL https://dev.meta.ai/install.sh | bash
  2. Ask Muse to add the server

    Start muse and ask:

    Add the Spiral MCP server at https://api.spiral.ai/mcp
  3. Sign in

    In your terminal, run:

    muse mcp login spiral

Use the Spiral skill

  1. Send Muse Code this message

    Your agent reads Spiral's skill and sets itself up.

    set up https://spiral.ai/SKILL.md
  2. Sign in or paste a key

    Approve Spiral in the browser, or give the agent a key from the console.

Use the Spiral CLI

  1. 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

  1. Create an API key

    In the console, under API keys.

  2. Run NOAA storm data publication status

    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/source_status",
        "input": {
          "type": "details"
        }
      }'

Then paste one of the prompts above: Muse Code finds NOAA storm data publication status on Spiral, shows the price and runs it.

NOAA storm data publication status providers and prices

Spiral runs NOAA storm data publication status through Alexandria. Open a card for today's price, with every fee included.

AlexandriaPublic Records
NOAA NCEI Storm Events Database bulk CSVs · Source status
ncei-noaa-gov/storm-events/source_status

Settings you can ask for

Ask Muse Code for any of these in your prompt.

SettingAllowed valuesDefaultDescription
Typedetails, locations, or fatalities

Narrow to one file type.

Year1950 to 2100

Data year (the d part of the file name), 1950 to the current year.

Every API field of NOAA NCEI Storm Events Database bulk CSVs · Source status is on its tool page: open its card above.

What can you do with NOAA storm data publication status 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.

Questions about NOAA storm data publication status in Muse Code

Can Muse Code use NOAA storm data publication status?

Yes. Add Spiral to Muse Code as an MCP server, and Muse Code can find and run NOAA storm data publication status like any built-in tool.

How much does NOAA storm data publication status 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 storm data publication status in Muse Code?

No. Spiral runs NOAA storm data publication status 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 storm data publication status 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 storm data publication status runs?

NOAA storm data publication status 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.

Get started

Start using NOAA storm data publication status 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 Muse Code

set up https://spiral.ai/SKILL.md
Are you an AI agent? See setup options