Skip to main content
Glama

FDA FAERS drug adverse event reports for a generic drug

health_fda_adverse_events_faers
Read-only

FDA FAERS drug adverse event reports (openFDA) for a generic drug name: report ID, receive date, seriousness, patient age and sex, drugs and reported reactions. Spontaneous reports only; a report does not prove the drug caused the reaction. Up to 10 reports per call. Related tools on this server, for a different need: health_fda_drug_shortages when you need FDA drug shortage listings: generic name, availability; health_fda_recalls_enforcement when you need FDA drug recall enforcement reports matching a product. Price: $0.002 per successful call, paid with x402 (USDC on Base, Solana and 10 more networks); failed calls are not charged.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "drug": "<drug>"
    },
    "name": "health_fda_adverse_events_faers"
  }
}

Input Schema

NameRequiredDescriptionDefault
maxNoHow many reports, 1 to 10 (default 5)
drugYesGeneric drug name, letters and spaces, 2 to 60 characters

Output Schema

NameRequiredDescriptionDefault
drugNo
totalNo
sourceNo
reportsNo
checkedAtNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Beyond the readOnlyHint/openWorldHint annotations it discloses the data-provenance caveat (spontaneous reports only, a report does not prove causation), the per-call cap of 10, and the billing model ($0.002 per successful call via x402 USDC across multiple networks, failures not charged) — real behavioral context an agent needs before invoking. The remaining gap is that it does not describe empty-result behavior or whether drug matching is exact or partial.

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?

Front-loaded with the resource and returned fields, then caveats, then sibling routing, then cost — a sensible priority order with no filler. The pricing sentence is the longest and slightly dense with network/billing detail, but it earns its place for a paid tool.

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, schema-documented tool with an output schema, the definition covers scope, caveats, limits, cost, and alternatives, so nothing critical is missing. Minor omissions remain around no-match behavior and name-matching strictness, which matter slightly for a free-text drug lookup.

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 both `drug` (generic name, 2–60 chars) and `max` (1–10, default 5) are already fully documented in the schema. The description only echoes the 10-report ceiling, which is the same fact encoded in `max`, so it adds no meaning beyond the schema 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?

States a specific verb and resource (retrieve FDA FAERS adverse event reports for a generic drug name) and enumerates the payload an agent will get back (report ID, receive date, seriousness, age/sex, drugs, reactions). It also explicitly separates itself from the two named siblings, so an agent can route without opening any schema.

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

Usage Guidelines5/5

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

Gives explicit routing conditions for the alternatives it names: use health_fda_drug_shortages for shortage listings and health_fda_recalls_enforcement for recall enforcement reports. That covers the realistic confusable needs for a drug-safety query, leaving no inference required about which tool to pick.

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.

Resources