Skip to main content
Glama

Stratalize Intelligence

Get Openfda Adverse Events

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/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is covered. The description adds genuinely useful context beyond that: the upstream source (OpenFDA), a per-call cost of $0.10 USDC, and a signed settlement receipt verifiable at a stated URL. What it omits is the freshness/latency of FAERS data and the threshold logic behind the signal levels, which materially affect interpretation of results.

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 what the tool returns, then source, then trust/pricing details. Every sentence carries information, though the settlement-receipt and verification sentence is dense and competes for attention with the actual data description.

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 usefully enumerates the return fields, and annotations cover mutability. But for a paid, externally-sourced, open-world lookup, the definition leaves the caller unsure what identifier form to pass and how to pick it over a sibling that appears functionally identical.

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% — the single parameter drug_name carries only type and length bounds, with no explanation of whether it accepts brand or generic names, casing behavior, or how matches are resolved. The description says only "for a drug" and does not compensate for that gap. For the one input the agent must supply, this is under-specified.

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?

Names a specific resource and verb-equivalent ("FDA FAERS adverse event signal for a drug") and enumerates the concrete outputs: total reports, serious events, deaths, hospitalizations, top reactions with percentages, and a HIGH/ELEVATED/MONITOR/LOW signal level. That is far more specific than the title. It does not, however, distinguish itself from the sibling get_drug_adverse_events, which appears to cover the same ground.

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 or when-not-to-use guidance, no prerequisites, and no routing to alternatives. With a near-identical sibling (get_drug_adverse_events) in the catalog, the absence of any disambiguation is a real cost to the agent. The only decision-relevant information given is the $0.10 USDC per-call price.

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