Skip to main content
Glama

get_drug_adverse_events

Read-only

FAERS drug adverse event reports from OpenFDA by medicinal product name. Returns serious event counts, reactions, outcomes, and recent report chronology. Use for pharmacovigilance monitoring, safety signal detection, and clinical risk agents. Source: FDA FAERS. $0.10 standard. Cryptographically attested with a post-quantum signed settlement receipt. Verify at trust.stratalize.com/verify.

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_drug_adverse_events"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
drug_nameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.1/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 needs no restatement. The description does add genuinely useful context beyond them: the payload contents (serious event counts, reactions, outcomes, chronology), the upstream source, and a per-call price of $0.10. It says nothing about pagination or how the limit affects result volume, which is the main remaining behavioral gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The opening sentence is well front-loaded and the return-value sentence is efficient. The closing attestation sentence ('cryptographically attested with a post-quantum signed settlement receipt. Verify at trust.stratalize.com/verify.') is promotional boilerplate that does not help an agent decide to call or how to call it, so it dilutes an otherwise tight definition.

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 correctly steps in to summarize return contents, and it discloses cost and provenance. But for a two-parameter tool with zero schema documentation, the unmentioned limit parameter and the lack of any guidance versus the overlapping sibling leave real gaps in what an agent needs to invoke this correctly.

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%, so the description carries the full param burden, and it only partially does: 'by medicinal product name' clarifies that drug_name expects a product name rather than an ingredient or NDC code. The limit parameter (1-100) is never mentioned, so its meaning, default, and effect on result size are undocumented everywhere.

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 definition states a specific resource (FAERS drug adverse event reports from OpenFDA) and the keying dimension (medicinal product name), which is clear enough to act on. It stops short of distinguishing itself from the near-identically named sibling get_openfda_adverse_events, so an agent cannot tell which of the two to pick from this text alone.

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

Usage Guidelines3/5

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

It lists intended applications (pharmacovigilance monitoring, safety signal detection, clinical risk agents), which implies when the tool fits. However, there is no when-not guidance, no prerequisites, and no routing to an alternative such as get_openfda_adverse_events or get_drug_recall_status, leaving overlap resolution entirely to inference.

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