Fda Drug Competition

Purple Book Biosimilars

purple_book_biosimilars

Read-onlyIdempotent

List FDA-licensed 351(k) biosimilar and interchangeable products for an optional reference product, applicant, or product name. Approval/licensure does not establish commercial launch or current availability.

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No	Rows (1-100, default 50).
`query`	No
`include_interchangeable`	No	Include interchangeable products (default true).

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

A4.6/5.0

Behavior5/5

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

Annotations already declare read-only, open-world, idempotent, and non-destructive behavior. The description adds a valuable real-world caveat: FDA licensure does not mean commercial launch or current availability, which is exactly the kind of behavioral context an agent needs when interpreting results.

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 two tight sentences: the first states the action and scope, the second provides a necessary interpretive caveat. No wasted words, and the most important information 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?

For a read-only listing tool with an output schema and strong annotations, the description covers the core purpose, filter semantics, and an important data-quality caveat. It is slightly less complete because it does not route the agent toward more specialized sibling tools, but nothing essential is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description defines what 'query' means (reference product, applicant, or product name), compensating for the schema's undocumented 'query' property. Both other parameters are already documented in the schema, so the description adds meaningful value without fully specifying matching behavior.

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 uses a specific verb ('List') with a clear resource ('FDA-licensed 351(k) biosimilar and interchangeable products') and names the optional filters (reference product, applicant, product name). This distinguishes it from sibling tools like purple_book_interchangeables or purple_book_reference_product.

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?

The description makes clear this is a list-oriented search with optional filters, and the approval-versus-availability caveat adds important usage context. However, it does not explicitly name sibling alternatives or state when to prefer a more specialized tool like purple_book_product_search.

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.