Skip to main content
Glama

Read a US drug's latest FDA label

fda_label
Read-only

The latest US drug label (FDA SPL) for a brand or generic name: brand, generic name, manufacturer, indications, dosage, warnings and contraindications (each cut to 1,000 characters) and the set id. Information from the label only; it is not medical advice. Source: openFDA. Information only, not medical advice. Related tools on this server, for a different need: fda_adverse_events when you need the most reported adverse reactions to a drug in FDA's. 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_label"
  }
}

Input Schema

NameRequiredDescriptionDefault
drugYesBrand or generic drug name, e.g. advil or ibuprofen

Output Schema

NameRequiredDescriptionDefault
drugNo
brandNo
setIdNo
dosageNo
sourceNo
genericNo
warningsNo
checkedAtNo
disclaimerNo
attributionNo
indicationsNo
manufacturerNo
effectiveTimeNo
contraindicationsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, but the description adds substantive behavior the annotations do not: each field is truncated to 1,000 characters, a set id is returned, the source is openFDA, and there is a per-call charge of $0.002 via x402 with failed calls not billed. That pricing and truncation context is genuinely useful for deciding whether to invoke it; the disclaimer is not behavioral information.

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 content list is well front-loaded, but the disclaimer is stated twice in near-identical wording ("it is not medical advice" and "Information only, not medical advice"), and the cross-reference sentence is visibly truncated. Those redundancies and the dangling clause cost clarity against an otherwise short description.

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

Completeness4/5

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

Output schema exists, so return-value explanation is not required, yet the description usefully previews fields and truncation, and covers cost and data provenance. Combined with a fully described single-param schema and safety annotations, an agent has enough to call it correctly; only the broken sibling sentence leaves a small gap.

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?

With one parameter at 100% schema description coverage, the schema already documents that the input is a brand or generic drug name with examples. The description restates the same 'brand or generic name' framing and adds no further syntax, normalization, or fallback guidance, so the baseline 3 applies.

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?

The first sentence names a specific verb and resource (the latest US drug label, FDA SPL) keyed by brand or generic name, and enumerates the returned fields (brand, generic, manufacturer, indications, dosage, warnings, contraindications, set id). It also explicitly sets itself apart from fda_adverse_events, so an agent can route without opening either schema.

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?

It gives an explicit alternative and a decision rule: use fda_adverse_events when the need is adverse-reaction reports rather than label content. What is missing is a stated when-not condition for this tool itself (e.g. non-US drugs or recalls), and the alternative sentence trails off mid-clause ("in FDA's."), which weakens the routing cue.

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