Skip to main content
Glama

get_openfda_adverse_events

Read-only

FDA FAERS adverse event signal for a drug — total reports, serious events, deaths, hospitalizations, top reactions with percentages, and signal level (HIGH / ELEVATED / MONITOR / LOW). Source: OpenFDA. Cryptographically attested with a post-quantum signed settlement receipt. Verify at trust.stratalize.com/verify. $0.10 USDC per call.

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_name": "<drug_name>"
    },
    "name": "get_openfda_adverse_events"
  }
}

Input Schema

NameRequiredDescriptionDefault
drug_nameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior4/5

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

Annotations already cover read-only, open-world, and non-destructive behavior, so the description's job is to add context beyond that — and it does: the upstream source (OpenFDA), a per-call price of $0.10 USDC, and a signed settlement receipt with a verification URL. These are material invocation facts (cost and provenance) an agent would not otherwise know. It does not mention rate limits, latency, or whether the $0.10 is charged on failure.

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 payload enumeration is front-loaded and separated by an em dash, so the agent reads the substance first. Source, attestation, and price follow in short sentences. The cryptographic-attestation sentence is somewhat promotional boilerplate but conveys a real property, so it earns partial keep.

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?

With no output schema, the description does a fair job sketching return fields and the signal-level scale. However, it leaves out the reporting time window covered by the counts, which is essential for interpreting adverse-event totals, and says nothing about drug_name formatting. Adequate but with clear interpretational gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% for the single required parameter, so the description must compensate and does not. It never states whether drug_name should be a brand name, generic name, active ingredient, or how misspellings/casing are handled — exactly the ambiguity that determines whether this call succeeds. It also omits any time-window parameter, which the described output implies exists.

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?

The description names a specific resource (FDA FAERS adverse event signal for a drug) and enumerates the payload: total reports, serious events, deaths, hospitalizations, top reactions with percentages, and a tiered signal level. That is far more concrete than the tool name alone. It stops short of 5 because it never distinguishes itself from the near-identical sibling get_drug_adverse_events, leaving the agent to guess which one to call.

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?

There is no explicit when-to-use, when-not-to-use, or alternative-naming guidance. The output enumeration implies the tool is for drug safety signal checks, but the agent must infer that. With a sibling named get_drug_adverse_events, the absence of any routing guidance is a real gap.

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