Skip to main content
Glama

search_drug_adverse_events

Search FDA adverse event reports to find side effects, reactions, and safety data for specific drugs by name, manufacturer, or other criteria.

Instructions

Search FDA drug adverse event reports (FAERS)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
drug_nameNoName of the drug or medication
brand_nameNoBrand/trade name of the drug
generic_nameNoGeneric name of the drug
manufacturerNoManufacturer name
reactionNoAdverse reaction or side effect
serious_onlyNoOnly return serious adverse events
patient_sexNoPatient sex (1=Male, 2=Female)
countryNoCountry where event occurred
date_fromNoStart date for date range (YYYYMMDD format)
date_toNoEnd date for date range (YYYYMMDD format)
countNoField to group results by for counting (e.g., "patient.drug.openfda.brand_name.exact")
limitNoMaximum number of results to return (1-100)
skipNoNumber of results to skip for pagination
Behavior1/5

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

With no annotations, the description bears full responsibility for behavioral disclosure. However, it only states the basic purpose with no details on pagination, rate limits, query behavior, or response format. This is insufficient for an agent to understand the tool's behavior.

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?

The description is a single, concise sentence that communicates the core purpose without unnecessary words.

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

Completeness1/5

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

Given the tool's complexity (13 parameters, no annotations, no output schema), the description is severely lacking. It does not explain how to effectively search, interpret results, or handle pagination. The agent would be left without critical usage information.

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?

All 13 parameters have descriptions in the schema (100% coverage), so the baseline is 3. The description adds no parameter-level context beyond the schema, so it remains at baseline.

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 the tool's function: 'Search FDA drug adverse event reports (FAERS)'. It uses a specific verb ('Search') and identifies the resource (FDA drug adverse event reports) and database (FAERS), distinguishing it from sibling tools like search_drug_labels or search_drug_recalls.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives. It does not mention prerequisites, when not to use, or how it relates to sibling tools. The context of sibling tools suggests differentiation by report type, but the description itself is silent.

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/Augmented-Nature/OpenFDA-MCP-Server'

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