Skip to main content
Glama

openFDA: Drug adverse events

openfda__drug-adverse-events
Read-onlyIdempotent

FAERS adverse event reports for a drug. Free within the daily allowance, then $0.003 USDC per call via x402.

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": {
      "search": "<search>"
    },
    "name": "openfda__drug-adverse-events"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax results (default 10, max 100)
searchYesopenFDA search expression

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds genuinely new behavioral context — a cost model (free within the daily allowance, then $0.003 USDC per call via x402), which matters for an agent deciding whether to call. It omits what the allowance actually is, auth requirements for x402, and result-set size behavior.

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?

Two sentences, purpose front-loaded, no filler. The pricing sentence earns its place by conveying a decision-relevant cost signal rather than restating metadata.

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?

An output schema exists so return values need no explanation, but the description leaves the openFDA query-expression convention entirely to the bare schema label, and gives no sibling routing. Adequate but with a clear gap where invocation correctness is concerned.

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% with only two parameters, so the baseline is 3. The description adds nothing about the openFDA search expression syntax, which is the one parameter most likely to be invoked incorrectly, and no guidance on the limit/pagination tradeoff.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific resource (FAERS adverse event reports) scoped to a drug, which is enough for an agent to distinguish it from siblings like drug-recalls, drug-labels, and device-events by resource name alone. It stops short of an explicit sibling comparison or an example of what an adverse event report contains.

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?

No when-to-use guidance, no mention of alternatives (e.g. drug-recalls for recall data, food-adverse-events for food), and no hint that the required 'search' parameter is how you bind the query to a specific drug. The only framing is pricing, which is not usage guidance.

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