Fda Drug Competition

Purple Book Product Search

purple_book_product_search

Read-onlyIdempotent

Search FDA Purple Book biologic products by proper/proprietary name, applicant, reference product, or BLA. Returns licensure and product-level attributes. A licensed biosimilar is not necessarily launched, available, interchangeable, or substitutable under state law.

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No	Rows (1-100, default 25).
`query`	Yes	Name, applicant, reference product, or BLA substring.
`license_type`	No
`include_discontinued`	No	Include discontinued products (default false).

Output Schema

TableJSON Schema

Name	Required	Description	Default
`source`	Yes
`products`	Yes
`returned`	Yes
`dataset_note`	No
`dataset_stale`	No
`dataset_updated`	No
`dataset_age_days`	No

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

Changed3 schema fields changedSep 2, 2026
- addedOutput schema / properties / dataset_age_days
```
Added value: +{
+  "type": [
+    "number",
+    "null"
+  ]
+}
```
- addedOutput schema / properties / dataset_note
```
Added value: +{
+  "type": "string"
+}
```
- addedOutput schema / properties / dataset_stale
```
Added value: +{
+  "type": "boolean"
+}
```
Changed1 schema field changedAug 6, 2026
- changedOutput schema / properties / dataset_updated / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
AddedJul 29, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the operation's safety profile is established. The description adds valuable context by stating that it returns licensure and product-level attributes, and it includes an important interpretive caveat that a licensed biosimilar is not necessarily launched, available, interchangeable, or substitutable. This goes beyond the structured metadata without contradicting it.

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?

The description is three sentences with no filler. The primary action and searchable fields are front-loaded, followed by a brief return-type statement and a useful legal caveat. Every sentence contributes meaning.

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?

Given that an output schema exists, the description does not need to detail return values. The presence of annotations covers safety and idempotency, and the description covers search scope and data interpretation caveats. It could be more complete by naming sibling tools or clarifying when the specialized Purple Book views should be preferred, but nothing essential is missing for invoking the 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 75%, so the schema already documents most parameters. The description mirrors the query parameter's allowed search fields (name, applicant, reference product, BLA) and adds 'proper/proprietary' specificity, but it does not materially extend the schema's parameter semantics for limit, license_type, or include_discontinued.

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 clearly identifies the verb (search), the resource (FDA Purple Book biologic products), and the search dimensions (name, applicant, reference product, BLA), making the tool's purpose easy to grasp. It is distinguishable from the sibling tools by its general product-search scope, though it does not explicitly name any sibling to differentiate itself.

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?

The description implies usage for searching Purple Book products by name or BLA, but it provides no explicit guidance on when to choose this tool over the many related sibling tools such as purple_book_biosimilars or purple_book_interchangeables. There are no exclusions or alternative recommendations, so usage context is only implicit.

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

All Fda Drug Competition tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.