Skip to main content
Glama

The most reported adverse reactions to a drug in FDA's

fda_adverse_events
Read-only

The most reported adverse reactions to a drug in FDA's FAERS database: counts, total reports and the share that were serious. Reports are voluntary and show association, not proof of cause. Source: openFDA. Information only, not medical advice. Related tools on this server, for a different need: fda_label when you need to read a US drug's latest FDA label. 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": "fda_adverse_events"
  }
}

Input Schema

NameRequiredDescriptionDefault
drugYesGeneric drug name, e.g. ibuprofen
limitNoTop reactions, 1 to 25 (default 10)

Output Schema

NameRequiredDescriptionDefault
drugNo
sourceNo
checkedAtNo
reactionsNo
disclaimerNo
attributionNo
totalReportsNo
seriousReportsNo
seriousSharePctNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint and openWorldHint, so the read-only, open-source nature is covered. The description nonetheless adds real value beyond them: voluntary reporting, association rather than causation, informational-only status, pricing at $0.002 per successful call, and that failed calls are not charged. It does not discuss pagination, rate limits, or data recency.

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 purpose and return fields, then caveats, then the sibling pointer. Nearly every sentence earns its place, though the pricing sentence is long and enumerates payment networks in more detail than an agent needs to select or call the tool.

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

Completeness5/5

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

An output schema exists, so return values need not be explained, yet the description still summarizes them. Combined with the data-source caveats, safety disclaimer, cost model, and sibling routing, an agent has everything needed to invoke it correctly.

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 parameters are documented in the schema, making 3 the baseline. The description adds no meaning about the drug parameter (generic vs brand naming) or the limit parameter's behavior, beyond repeating that results are per drug.

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 resource (most reported adverse reactions for a drug in FAERS) plus exactly what is returned: counts, total reports, and share serious. It also names the sibling fda_label and the different need that selects it, so an agent can distinguish the two without opening schemas.

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

Usage Guidelines4/5

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

Gives explicit routing to the alternative tool (fda_label for reading a US drug's latest FDA label), which covers the most likely confusion. It stops short of stating when not to use this tool, such as for causality questions or non-FAERS sources, so it is strong but not exhaustive.

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