Skip to main content
Glama

search_fda_purple_book

Search FDA Purple Book licensed biological products by name, applicant, BLA number, license type, biosimilar or interchangeability status; returns product, licensing, and reference details.

Instructions

Search FDA Purple Book for licensed biological products. Find biologics by product name, applicant, BLA number, license type (351(a)/351(k)), biosimilar status, or interchangeability. Returns product details, licensing status, and reference product information.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search_fda_purple_book"
  }
}

Input Schema

NameRequiredDescriptionDefault
skipNoNumber of results to skip for pagination
limitNoMaximum results to return (1-100, default 10)
applicantNoApplicant/company name
blaNumberNoBiologics License Application (BLA) number
biosimilarNoFilter for biosimilar products
licenseTypeNoLicense type: 351(a) for originator, 351(k) for biosimilar
productNameNoProduct proprietary or proper name to search
interchangeableNoFilter for interchangeable products

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.2.2
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  2. First observedv1.2.0

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden. It does disclose the return contents ('product details, licensing status, and reference product information'), which is genuinely useful, but it omits that this is a read-only lookup with no side effects, how results are ordered, and what the default result count is (the schema sets a default of 10 and a cap of 100).

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?

Three tightly packed sentences with no filler: purpose first, supported filters second, return values third. Every sentence contributes information the agent needs and the key scope statement is front-loaded.

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 8 optional parameters, no annotations, and no output schema, the description does reasonably well by naming the filter set and the shape of the response. It falls slightly short on query semantics (can all filters be empty? how are results ordered/paginated?) for a search tool with this many knobs.

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 every parameter is already documented, including the 351(a)/351(k) license-type semantics and the biosimilar/interchangeable booleans. The description mirrors those concepts rather than adding new meaning such as matching behavior for productName or how applicant strings are matched.

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 description states a specific verb and resource ('Search FDA Purple Book for licensed biological products') and enumerates the searchable dimensions (product name, applicant, BLA number, license type, biosimilar status, interchangeability). It does not explicitly contrast itself with the Orange Book siblings, so an agent must infer that this covers biologics rather than small-molecule drugs.

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?

Usage is implied by the list of supported filters, which tells the agent what kinds of queries this tool answers. There is no explicit when-to-use vs. when-not guidance, no mention of search_fda_orange_book as the alternative for non-biologic drugs, and no statement about whether a query with zero filters is permitted.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.