Skip to main content
Glama

FDA Drugs@FDA approved applications by active ingredient

health_fda_orange_book
Read-only

FDA Drugs@FDA approved applications (openFDA) by active ingredient: application number, sponsor, brand names, dosage form, marketing status and Orange Book therapeutic equivalence (TE) code. Up to 10 applications per call. Related tools on this server, for a different need: health_fda_purple_book when you need FDA Purple Book licensed biological products matching; health_fda_adverse_events_faers when you need FDA FAERS drug adverse event reports for a generic drug. 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": {
      "ingredient": "<ingredient>"
    },
    "name": "health_fda_orange_book"
  }
}

Input Schema

NameRequiredDescriptionDefault
maxNoHow many applications, 1 to 10 (default 5)
ingredientYesActive ingredient name, letters and spaces, 2 to 60 characters

Output Schema

NameRequiredDescriptionDefault
totalNo
sourceNo
checkedAtNo
ingredientNo
applicationsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Beyond the readOnlyHint/openWorldHint annotations, the description discloses a per-call cap (up to 10 applications), the price ($0.002 per successful call), the payment mechanism (x402, USDC on Base/Solana and other networks), and that failed calls are not charged -- material context an agent needs before calling. It stops short of noting rate limits or upstream data-lag characteristics.

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 purpose and field list are front-loaded, with sibling disambiguation and pricing following in logical order. The payment sentence is comparatively long, but every clause (price, mechanism, networks, failure policy) carries operational value.

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?

With an output schema covering return values, full parameter documentation, and read-only annotations, the description supplies what remains: scope, field coverage, call cap, sibling routing, and billing behavior. Little an agent needs to invoke it correctly is missing.

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%, so both parameters (ingredient, max) are already fully documented with ranges and format. The description only echoes the maximum of 10 via the per-call cap, adding no syntax or edge-case guidance beyond the schema, which is the expected baseline.

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 description states a specific verb and resource -- retrieving FDA Drugs@FDA approved applications by active ingredient -- and enumerates the returned fields (application number, sponsor, brand names, dosage form, marketing status, TE code). It is clearly distinguishable from siblings like health_fda_purple_book and health_fda_adverse_events_faers, which are explicitly characterized as serving different needs.

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 explicit routing guidance for two alternatives with the condition that selects them: Purple Book for licensed biological products, FAERS for adverse event reports on a generic drug. The tool's own applicability is conveyed through the scope phrase 'by active ingredient', though no explicit exclusion or negative condition for this tool itself is 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