Skip to main content
Glama

SolvingHealth federal health data

search_adverse_events

Search FDA MAUDE device adverse event reports. Use for real-world failure modes reported for a device type.

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_adverse_events"
  }
}

Input Schema

NameRequiredDescriptionDefault
qNoGeneric device name, e.g. "knee prosthesis"
limitNoMax results, 1-50

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are provided, so the description carries the burden, but a search over public FDA reports is inherently low-risk and 'search' plus the named dataset already signals read-only behavior. It omits what the result set looks like, whether results are ranked or date-ordered, and what the default limit is, which leaves real gaps for an agent planning a call.

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?

Two tight sentences with zero filler, and the data source is front-loaded ahead of the use case. Nothing could be removed without losing information.

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 two-parameter, read-only search tool with no output schema and optional inputs, the definition covers source and intent adequately. It is only slightly short on result-shape and default behavior, which matter because both parameters are optional and a call with no arguments is legal.

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 coverage is 100% and both parameters carry their own descriptions plus a bound on limit, so the schema does the heavy lifting. The description adds nothing beyond the schema, such as how free-text matching works or what value is used when q is omitted, so the baseline 3 applies.

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

Purpose4/5

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

Names a specific verb and resource ('Search FDA MAUDE device adverse event reports'), which pins the underlying data source unambiguously. The second sentence narrows it to real-world failure modes, implicitly separating it from sibling sources like recalls and clearances, though it never names a sibling explicitly.

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?

'Use for real-world failure modes reported for a device type' is a genuine usage hint rather than a bare restatement. However, it gives no when-not guidance and does not say how to choose between this and search_device_recalls or search_clearances, which surface overlapping safety signals.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.