[Integrations](https://spiral.ai/integrations) › [opencode](https://spiral.ai/integrations/opencode) › [FDA medical device adverse event reports](https://spiral.ai/integrations/opencode/fda-medical-device-adverse-event-reports)

# How to Use FDA medical device adverse event reports in opencode

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.

|  |  |
| --- | --- |
| Model | FDA medical device adverse event reports |
| Available through | Alexandria |
| Category | Health |
| Price | $0.00873 per call. |
| Returns | json |
| Runs | In the background |
| Setup | About 2 minutes, no API key |

## Prompts to try with FDA medical device adverse event reports in opencode

- 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 opencode

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

### Use Spiral's MCP server

1. **Add the server**: Leave out `--global` to add Spiral to the current project only. No header and no client ID or secret: opencode registers itself with Spiral.

```bash
opencode mcp add spiral --global --url https://api.spiral.ai/mcp
```

2. **Sign in**: Your browser opens. Sign in to Spiral, pick the organization and click Authorize, then return to the terminal. No API key. Inside opencode, `/mcps` starts the same sign-in.

```bash
opencode mcp auth spiral
```

3. **Check it**: Spiral shows as connected.

```bash
opencode mcp list
```

### Use the Spiral skill

1. **Send opencode 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.

```bash
npx -y spiral-cli@latest init
```

### Call the Spiral API

1. **Create an API key**: In the console, under API keys.

2. **Run FDA medical device adverse event reports**: One request; the result comes back by polling or a webhook.

```bash
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: opencode finds FDA medical device adverse event reports on Spiral, shows the price and runs it.

Setup guide in the docs: https://spiral.ai/docs/quickstarts/opencode

## FDA medical device adverse event reports tools and prices

- [FDA · Device events](https://spiral.ai/tools/alexandria/fda-gov/adverse-events/device_events) (Alexandria): $0.00873 per call.

## Settings you can ask for

| Setting | Allowed values | Default | Description |
| --- | --- | --- | --- |
| skip | 0 to 25000 | 0 | skip |
| limit | 1 to 100 | 10 | limit |
| query |  | — | Words that must all appear in the narratives; wrap a phrase in double quotes, e.g. "sensor error" adhesive. |
| device |  | — | Brand or generic name words, matched as a phrase, e.g. Dexcom G7 or insulin pump. |
| count_by | event_type, product_problem, patient_problem, manufacturer, brand_name, product_code, 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. |
| report_id |  | — | MDR report key, e.g. 23938785, or report number, e.g. 3004753838-2025-353233. |

## What can you do with FDA medical device adverse event reports in opencode?

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.

## Overview

- [Alexandria](https://spiral.ai/providers/alexandria)
- [All opencode guides](https://spiral.ai/integrations/opencode)

## FDA medical device adverse event reports in other agents

- [Amp](https://spiral.ai/integrations/amp/fda-medical-device-adverse-event-reports)
- [ChatGPT](https://spiral.ai/integrations/chatgpt/fda-medical-device-adverse-event-reports)
- [Claude](https://spiral.ai/integrations/claude-desktop/fda-medical-device-adverse-event-reports)
- [Claude Code](https://spiral.ai/integrations/claude-code/fda-medical-device-adverse-event-reports)
- [Cline](https://spiral.ai/integrations/cline/fda-medical-device-adverse-event-reports)
- [Codex](https://spiral.ai/integrations/codex/fda-medical-device-adverse-event-reports)
- [Cursor](https://spiral.ai/integrations/cursor/fda-medical-device-adverse-event-reports)
- [Devin](https://spiral.ai/integrations/devin/fda-medical-device-adverse-event-reports)
- [dots](https://spiral.ai/integrations/dots/fda-medical-device-adverse-event-reports)
- [Factory Droid](https://spiral.ai/integrations/factory-droid/fda-medical-device-adverse-event-reports)
- [Gemini](https://spiral.ai/integrations/gemini/fda-medical-device-adverse-event-reports)
- [Gemini CLI](https://spiral.ai/integrations/gemini-cli/fda-medical-device-adverse-event-reports)
- [Google Antigravity](https://spiral.ai/integrations/antigravity/fda-medical-device-adverse-event-reports)
- [goose](https://spiral.ai/integrations/goose/fda-medical-device-adverse-event-reports)
- [Grok](https://spiral.ai/integrations/grok/fda-medical-device-adverse-event-reports)
- [Grok Build](https://spiral.ai/integrations/grok-build/fda-medical-device-adverse-event-reports)
- [Hermes](https://spiral.ai/integrations/hermes/fda-medical-device-adverse-event-reports)
- [Instinct](https://spiral.ai/integrations/instinct/fda-medical-device-adverse-event-reports)
- [Manus](https://spiral.ai/integrations/manus/fda-medical-device-adverse-event-reports)
- [Muse](https://spiral.ai/integrations/muse/fda-medical-device-adverse-event-reports)
- [Muse Code](https://spiral.ai/integrations/muse-code/fda-medical-device-adverse-event-reports)
- [n8n](https://spiral.ai/integrations/n8n/fda-medical-device-adverse-event-reports)
- [Notion](https://spiral.ai/integrations/notion/fda-medical-device-adverse-event-reports)
- [OpenClaw](https://spiral.ai/integrations/openclaw/fda-medical-device-adverse-event-reports)
- [Perplexity](https://spiral.ai/integrations/perplexity/fda-medical-device-adverse-event-reports)
- [Raycast](https://spiral.ai/integrations/raycast/fda-medical-device-adverse-event-reports)
- [VS Code](https://spiral.ai/integrations/vscode/fda-medical-device-adverse-event-reports)
- [Windsurf](https://spiral.ai/integrations/windsurf/fda-medical-device-adverse-event-reports)
- [Zapier](https://spiral.ai/integrations/zapier/fda-medical-device-adverse-event-reports)

## More opencode guides

- [FDA food recall records](https://spiral.ai/integrations/opencode/fda-food-recall-records)
- [FDA medical device classifications](https://spiral.ai/integrations/opencode/fda-medical-device-classifications)
- [FDA first generic drug approvals](https://spiral.ai/integrations/opencode/fda-first-generic-drug-approvals)
- [FDA medical device recall reports](https://spiral.ai/integrations/opencode/fda-medical-device-recall-reports)
- [FDA drug shortage records](https://spiral.ai/integrations/opencode/fda-drug-shortage-records)
- [FDA novel drug approvals](https://spiral.ai/integrations/opencode/fda-novel-drug-approvals)

## Questions about FDA medical device adverse event reports in opencode

**Can opencode use FDA medical device adverse event reports?**

Yes. Add Spiral to opencode as an MCP server, and opencode 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 opencode?**

$0.00873 per call. You pay from your Spiral balance as you go, with no subscription, and a failed run is not charged. Your opencode plan is separate.

**Do I need an Alexandria account to use FDA medical device adverse event reports in opencode?**

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 opencode?**

About two minutes: add the server, then sign in, then check it.

**Does opencode wait while FDA medical device adverse event reports runs?**

FDA medical device adverse event reports runs in the background. opencode 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.

