How to Use FDA medical device adverse event reports in Muse Code
Returns medical device reports from FDA's MAUDE database, including event narratives, device details, reported problems, and grouped counts. Use it to investigate reported device problems or prepare a safety review.
Prompts to try with FDA medical device adverse event reports in Muse Code
Copy an example into Muse Code, or ask in your own words.
Use FDA medical device adverse event reports to fetch Dexcom G7 reports received through October 31, 2026, and add a review table to this project with report keys, device details, and narrative summaries.
Use FDA medical device adverse event reports to retrieve grouped product problem counts for Medtronic and build a chart in this project labeled as report counts.
Use FDA medical device adverse event reports to search insulin pump narratives for "occlusion" and create a local review file containing each returned report key and a short description.
Use FDA medical device adverse event reports to fetch Abbott FreeStyle Libre reports and add a project view that keeps each narrative beside its device details.
Use FDA medical device adverse event reports to retrieve Dexcom G7 reports and compare their MDR report keys with the project's saved review queue, identifying returned reports already reviewed.
How to set up FDA medical device adverse event reports 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 FDA medical device adverse event reports
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": "fda-gov/adverse-events/device_events", "input": { "skip": 0 } }'
Then paste one of the prompts above: Muse Code finds FDA medical device adverse event reports on Spiral, shows the price and runs it.
FDA medical device adverse event reports providers and prices
Spiral runs FDA medical device adverse event reports 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 |
|---|---|---|---|
| Skip | 0 to 25000 | 0 | skip |
| Limit | 1 to 100 | 10 | limit |
| Count by | event_type, product_problem, patient_problem, manufacturer, brand_name, product_code, or received_month | Return counts of matching reports by this field instead of reports; limit caps the number of terms (not months), and skip must be 0. | |
| Event type | death, injury, malfunction, other, or no_answer | event_type |
Every API field of FDA · Device events is on its tool page: open its card above.
What can you do with FDA medical device adverse event reports in Muse Code?
Build a searchable review table of MAUDE narratives and device details in your project. Use MDR report keys to recognize reports across refreshes and label count charts as reporting activity.
Prepare a device problem review
Collect reports mentioning Dexcom G7, summarize the reported problems, and attach report keys to the narratives selected for review.
Build a manufacturer briefing
Summarize the device problems reported for Medtronic and select supporting narratives for a quality team's reading list.
Investigate a recurring narrative theme
Search insulin pump reports for occlusion language and organize the returned descriptions into themes for further investigation.
Monitor reported problem counts
Repeat the same device search each week and compare grouped problem counts with the previous run. Present changes as reporting activity rather than failure rates.
Support purchasing research
Prepare separate reported-problem summaries for device brands under consideration, with supporting narratives and no ranking by failure rate.
Assemble a report review queue
Turn returned reports into a review queue keyed by MDR report key, keeping device details and event narratives together for follow-up.
More on FDA medical device adverse event reports and Muse Code
Overview
FDA medical device adverse event reports in other agents
Questions about FDA medical device adverse event reports in Muse Code
Can Muse Code use FDA medical device adverse event reports?
Yes. Add Spiral to Muse Code as an MCP server, and Muse Code can find and run FDA medical device adverse event reports like any built-in tool.
How much does FDA medical device adverse event reports 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 FDA medical device adverse event reports in Muse Code?
No. Spiral runs FDA medical device adverse event reports on its own Alexandria account. You sign in to Spiral once and never paste a key.
How long does it take to set up FDA medical device adverse event reports in Muse Code?
About two minutes: install Muse Code, then ask Muse to add the server, then sign in.
Does Muse Code wait while FDA medical device adverse event reports runs?
FDA medical device adverse event reports runs in the background. Muse Code starts the run, checks on it and gives you the json when it's ready.
Whose reports does MAUDE contain?
MAUDE includes reports from mandatory reporters such as manufacturers, importers, and device user facilities. It also includes voluntary reports from health professionals, patients, and consumers.
How often does the data update?
FDA documents weekly updates for the openFDA device adverse event data. That schedule describes dataset updates, rather than when the reported events happened.
Can report counts tell me a device's failure rate?
No. FDA explicitly states that MDR data alone cannot establish event rates, so a larger report count does not establish a higher failure rate.
Why might a device name search miss reports?
FDA says variations in trade, product, and company names affect MAUDE search results. Search the brand, generic device description, and relevant company spellings separately before drawing conclusions from an empty result.
Does a follow-up report get a new MDR report key?
No. FDA states that follow-up reports do not change the MDR report key, which makes that key useful for recognizing a report across repeated reviews.
Start using FDA medical device adverse event reports 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


