Skip to main content
Glama

search_device_adverse_events

Find FDA medical device adverse event reports by device name, brand, manufacturer, event type, or date, and retrieve a specific MDR report by report number.

Instructions

Search FDA Medical Device Report (MDR) database for device adverse events. Find adverse events by device name, brand, manufacturer, event type (Injury/Death/Malfunction), and date. Retrieve a specific MDR report by reportNumber. Returns device details, event descriptions, and patient outcomes.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search_device_adverse_events"
  }
}

Input Schema

NameRequiredDescriptionDefault
skipNoNumber of results to skip for pagination
limitNoMaximum results to return (1-100, default 10)
dateToNoEnd date (YYYY-MM-DD or YYYYMMDD format)
dateFromNoStart date (YYYY-MM-DD or YYYYMMDD format)
brandNameNoDevice brand name
eventTypeNoType of adverse event
deviceNameNoDevice generic name
reportNumberNoMDR report number for retrieving a specific device adverse event report
manufacturerNameNoDevice manufacturer name

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.2.2
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  2. First observedv1.2.0

TDQS

A3.8/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the full burden: it does disclose the return contents ('device details, event descriptions, and patient outcomes') and that this is a retrieval operation over a public FDA database. It does not say how multiple filters combine, what happens when no filters are supplied, or how pagination behaves beyond what the schema already states.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences, front-loaded with the primary search purpose, then the lookup mode, then return contents. No filler or redundant restatement of the name.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 9-parameter, all-optional search tool with no output schema, the description covers purpose, filterable dimensions, lookup mode, and return shape. The remaining gap is default behavior when no filters are given and how results are ordered, which matters for a tool where every parameter is optional.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the baseline is 3. The description restates the filterable fields and enumerates event types, but omits 'Other' which the schema enum includes, and adds no semantics beyond the schema (e.g., match behavior for deviceName vs brandName vs manufacturerName).

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Search FDA Medical Device Report (MDR) database for device adverse events') and enumerates the searchable dimensions plus the reportNumber lookup mode. The word 'device' cleanly separates it from search_drug_adverse_events without needing to open either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied clearly enough by the two modes described (filter-based search vs. retrieve by reportNumber), but there is no explicit when-to-use guidance, no statement of which sibling to prefer for adjacent questions, and no exclusion such as whether reportNumber should be used alone.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.