Skip to main content
Glama

FDA Purple Book licensed biological products matching

health_fda_purple_book
Read-only

FDA Purple Book licensed biological products matching a name (brand or proper name, e.g. adalimumab): applicant, BLA number, license type (351(a) originator, 351(k) biosimilar or interchangeable), strength, dosage form, route, marketing status, approval date, reference product and exclusivity expiry dates, plus the products newly approved or updated this month. From FDA's monthly Purple Book data download. Related tools on this server, for a different need: health_fda_orange_book when you need FDA Drugs@FDA approved applications by active ingredient; health_fda_recalls_enforcement when you need FDA drug recall enforcement reports matching a product. 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": {
      "name": "<name>"
    },
    "name": "health_fda_purple_book"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesBrand or proper (nonproprietary) name, or BLA number (required)
limitNoProducts to return, 1 to 100 (default 25)

Output Schema

NameRequiredDescriptionDefault
countNo
queryNo
totalNo
reportNo
sourceNo
productsNo
checkedAtNo
changedThisMonthNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations only declare readOnlyHint and openWorldHint; the description adds the material behavioral facts an agent cannot get elsewhere: monthly data freshness from the Purple Book download, inclusion of newly approved/updated products this month, a metered cost of $0.002 per successful call, x402 payment requirements (USDC on Base/Solana and 10 more networks), and that failed calls are not charged. That is genuine auth/cost/freshness disclosure beyond the annotation surface.

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?

Front-loaded with purpose, then output fields, then freshness/source, then sibling routing, then price; every sentence carries distinct information and none is redundant with the schema. The long field enumeration is dense but it is the highest-value content for selecting the tool.

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

Completeness5/5

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

For a two-parameter read-only lookup with an output schema and safety annotations, nothing essential is missing: the description covers what it returns, how fresh the data is, what it costs, and when to prefer a sibling. Return-value detail is delegated correctly to the output schema.

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 coverage is 100% and both parameters are documented in-schema (name accepts brand, proper name, or BLA; limit 1-100 default 25). The description adds only a worked example ('e.g. adalimumab') and does not clarify format constraints, matching behavior (exact vs partial), or what happens with ambiguous names, 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?

States a specific verb and resource ('FDA Purple Book licensed biological products matching a name') and immediately enumerates the returned attributes (applicant, BLA number, license type 351(a)/351(k), strength, dosage form, route, marketing status, approval date, reference product, exclusivity dates). It also names the sibling it is not (health_fda_orange_book) with the distinguishing condition, 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 Guidelines5/5

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

Explicitly routes between alternatives with conditions: use health_fda_orange_book 'when you need FDA Drugs@FDA approved applications by active ingredient' and health_fda_recalls_enforcement 'when you need FDA drug recall enforcement reports'. It also implies the primary use case (identify a biological product by brand/proper name or BLA and get its licensure/exclusivity picture).

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