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

Muse Code · Public Records

How to Use GDACS disaster catalogue status in Muse Code

Returns source status and event-count information for a selected year. Use it before an archive collection to understand the expected volume and check whether the catalogue has changed.

Prompts to try with GDACS disaster catalogue status in Muse Code

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

Use GDACS disaster catalogue status for 2025 and show the returned annual count information in our project's archive import preview.

GDACS disaster catalogue statusMuse Code
Try asking
  • Use GDACS disaster catalogue status to look this up and give me the result as a table. Save the result in ./assets.

  • Pull the latest numbers from GDACS disaster catalogue status and tell me what changed since last week.

  • Check GDACS disaster catalogue status and summarize what you find in three bullet points.

  • Pull the newest data from GDACS disaster catalogue status and give me the result as a table.

How to set up GDACS disaster catalogue 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 GDACS disaster catalogue 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": "gdacs-org/disaster-alerts/source_status",
        "input": {
          "year": 2000
        }
      }'

Then paste one of the prompts above: Muse Code finds GDACS disaster catalogue status on Spiral, shows the price and runs it.

GDACS disaster catalogue status providers and prices

Spiral runs GDACS disaster catalogue status through Alexandria. Open a card for today's price, with every fee included.

AlexandriaPublic Records
GDACS global multi-hazard alerts · Source status
gdacs-org/disaster-alerts/source_status

Settings you can ask for

Ask Muse Code for any of these in your prompt.

SettingAllowed valuesDefaultDescription
Year2000 to 2100

Statistic year. Default: the current year, year-to-date.

Every API field of GDACS global multi-hazard alerts · Source status is on its tool page: open its card above.

What can you do with GDACS disaster catalogue status in Muse Code?

Build a disaster event dashboard that shows GDACS assessments and available footprints alongside public infrastructure. Your coding agent can populate a historical collection, apply revisions, and add event detail views to the project.

Maintain a disaster monitoring dashboard

Check catalogue status, collect a baseline archive, search the countries being monitored, inspect selected events, and apply subsequent changes to keep the dashboard current.

Build a reviewed annual disaster archive

Use annual status information to plan collection, gather the year's events, search for review samples, inspect their details, and incorporate later revisions before publishing the analysis.

Prepare recurring country briefings

Maintain a dated event collection, check source status, find relevant country alerts, examine the events behind the briefing, and update the draft when GDACS revises them.

Review exposure around public infrastructure

Build and refresh a disaster event collection, use catalogue status to check collection scope, search relevant countries, and inspect available event footprints alongside ports, airports, or other public infrastructure.

Compare historical event collections

Collect matching periods in different years and compare the GDACS events recorded in each. Describe the result as a comparison of GDACS records, given its stated completeness limits.

Questions about GDACS disaster catalogue status in Muse Code

Can Muse Code use GDACS disaster catalogue status?

Yes. Add Spiral to Muse Code as an MCP server, and Muse Code can find and run GDACS disaster catalogue status like any built-in tool.

How much does GDACS disaster catalogue 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 GDACS disaster catalogue status in Muse Code?

No. Spiral runs GDACS disaster catalogue 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 GDACS disaster catalogue 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 GDACS disaster catalogue status runs?

GDACS disaster catalogue status runs in the background. Muse Code starts the run, checks on it and gives you the json when it's ready.

Does GDACS provide confirmed disaster damage totals?

GDACS calculates potential impact using hazard characteristics, population exposure, and vulnerability. Its terms require confirmation before notifications or automatic impact estimates are used for decisions.

How fresh is GDACS information?

GDACS describes its notifications as near-real-time, but explicitly gives no guarantee of completeness or timeliness. A recent retrieval does not establish that every relevant event or revision is already present.

What does an active event mean on the GDACS homepage?

The MHEWS homepage requires an update within the last four days, except for droughts, where the window is ten days. That label reflects recent monitoring activity rather than proof that a hazard has ended.

Can a GDACS search return more than 100 events?

The upstream search returns the first 100 results and supports pagination. A single result page should not be treated as the full historical collection.

Does GDACS cover tropical cyclones outside the Atlantic?

Yes. GDACS documents worldwide tropical cyclone coverage using NOAA and Joint Typhoon Warning Center bulletins.

Get started

Start using GDACS disaster catalogue 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