Skip to main content
Glama

search_drug_adverse_events

Search FDA adverse event reports by drug name, reaction, manufacturer, date range, or seriousness, and retrieve specific safety reports to investigate drug safety signals.

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.

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_drug_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)
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

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.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 must carry the full behavioral burden. It discloses the response categories (patient demographics, drug details, reported reactions), but omits pagination behavior, result limits, sorting, authentication requirements, and does not explicitly confirm the read-only nature of the operation.

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

Conciseness4/5

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

The description is front-loaded with the tool's purpose and stays to four sentences with no filler. The filter enumeration in the second sentence overlaps somewhat with the schema, but overall it is efficient and easy to scan.

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

Completeness3/5

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

For a nine-parameter search tool with no output schema and no annotations, the description is adequate but incomplete. It summarizes the return categories but does not explain result ordering, pagination mechanics, or the level of detail in the response, leaving gaps an agent would need to discover by invocation.

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 schema already documents all nine parameters. The description restates the filterable dimensions but adds no syntax, format, or semantic details beyond what the schema already provides; 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?

States a specific verb and resource: searches FAERS for drug safety reports, and names the retrievable entity (adverse event report). The purpose is distinguishable from siblings like search_drug_labels or search_drug_recalls because it explicitly targets adverse event reports.

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?

Provides implied usage by listing the filterable fields and noting that a specific report can be retrieved via safetyReportId. However, it gives no explicit guidance on when to choose this tool over related siblings (e.g., drug labels, recalls) or any exclusions.

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