Skip to main content
Glama

openFDA: Drug approvals

openfda__drugs-fda
Read-onlyIdempotent

FDA approval history (Drugs@FDA) for an application or brand. 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__drugs-fda"
  }
}

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

A3.5/5.0
Behavior4/5

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

Annotations already carry the safety profile (readOnly, idempotent, openWorld, non-destructive), so the description adds value by disclosing the cost model: free within a daily allowance, then $0.003 USDC per call via x402. That is exactly the kind of operational context annotations cannot express. It falls short of a 5 only because it says nothing about pagination behavior or result-volume expectations.

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

Conciseness5/5

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

Two sentences, no filler, and the function ('FDA approval history for an application or brand') is front-loaded ahead of the billing note. Every clause carries information the agent needs.

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 needn't be explained, and annotations cover the safety profile. However, the tool is search-driven and the description gives no orientation on the openFDA search expression syntax or result scoping, and it never routes the agent away from the many adjacent openFDA drug endpoints — a meaningful gap for a 2-param query tool.

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% for both parameters (limit and search), so the schema already does the heavy lifting — baseline 3. The description's mention of 'an application or brand' hints at what the search expression should target but adds no actual syntax or format guidance beyond the schema's 'openFDA search expression'.

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 verb+resource: 'FDA approval history (Drugs@FDA) for an application or brand.' An agent can tell this is approval/regulatory-history data rather than labels, NDC codes, recalls, or adverse events. It does not, however, explicitly name or contrast with the nearest siblings (drug-labels, drug-ndc), so it stops short of a 5.

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 when-to-use guidance, no when-not-to-use, and no reference to any alternative tool. The agent must infer from the phrase 'approval history' that this is the right endpoint versus openfda__drug-labels or openfda__drug-ndc. No prerequisites or eligibility conditions are stated.

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