Skip to main content
Glama
sapientsai

OpenFDA MCP Server

by sapientsai

search_drug_adverse_events

Search FDA FAERS for adverse event reports by drug name, reaction, or manufacturer. Retrieve patient demographics, drug details, and reported reactions.

Instructions

Search FDA Adverse Event Reporting System (FAERS) for drug safety reports. Find adverse events by drug name, reaction type, manufacturer, date range, and seriousness. Retrieve a specific report by safetyReportId. Returns patient demographics, drug details, and reported reactions.

Input Schema

TableJSON 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)
seriousNoFilter for serious adverse events only
dateFromNoStart date (YYYY-MM-DD or YYYYMMDD format)
drugNameNoDrug or product name to search
reactionNoAdverse reaction to search (e.g., 'headache', 'nausea')
manufacturerNoDrug manufacturer name
safetyReportIdNoUnique safety report ID for retrieving a specific adverse event report
Behavior3/5

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

With no annotations provided, the description is the sole source of behavioral information. It discloses return content (patient demographics, drug details, reactions) but omits rate limits, authentication needs, or restrictions. The tool is clearly read-only, but this is not explicitly stated.

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 efficiently convey purpose, parameters, and return values. No unnecessary words; all sentences add value. Front-loaded with the main action.

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?

Given no output schema and no annotations, the description adequately covers return fields. However, it does not mention pagination behavior (skip, limit) or date format specifics, which are in the schema but could be highlighted for completeness.

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?

Input schema has 100% coverage with descriptions for all 9 parameters. The description adds a summary narrative grouping parameters (e.g., 'by drug name, reaction type, manufacturer') but does not provide additional detail beyond the schema. Baseline 3 is appropriate.

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?

The description clearly states it searches FAERS for drug safety reports, specifying key parameters (drug name, reaction, manufacturer, date range, seriousness) and the ability to retrieve by safetyReportId. It distinguishes from sibling tools by focusing on drug adverse events, as seen in sibling names like 'search_device_adverse_events'.

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?

The description implies usage for drug adverse events but does not explicitly state when to use this tool versus alternatives like 'search_device_adverse_events'. No when-not-to-use or exclusion criteria are provided.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/sapientsai/openfda-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server