Fda Drug Competition

Purple Book Reference Product

purple_book_reference_product

Read-onlyIdempotent

Find a reference biologic and its FDA-licensed 351(k) products by proper or proprietary name. Product rows and BLA counts must not be interpreted as market participants, launches, or market share.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`limit`	No
`reference_product`	Yes

Output Schema

TableJSON Schema

Name	Required	Description	Default
`source`	Yes
`dataset_note`	No
`dataset_stale`	No
`interpretation`	Yes
`dataset_updated`	No
`dataset_age_days`	No
`unique_351k_blas`	Yes
`reference_product`	Yes
`reference_products`	Yes
`related_351k_products`	Yes

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"
+}
```
AddedJul 29, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare the tool read-only, idempotent, and non-destructive. The description adds valuable context by warning that 'Product rows and BLA counts must not be interpreted as market participants, launches, or market share,' preventing misinterpretation of regulatory data. This goes beyond the basic safety profile provided by annotations.

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 sentences with no filler: the first states the core action and target, the second provides an essential interpretive warning. Both sentences earn their place, and the key function 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?

Given the tool's simplicity, the presence of an output schema, and comprehensive read-only annotations, the description is largely complete. It covers the search action and an important caveat about data interpretation. The main missing elements are explicit guidance on when to use this tool versus similar purple_book tools and any explanation of the limit parameter.

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?

With 0% schema description coverage, the description must compensate. It does add meaning to reference_product by specifying lookup 'by proper or proprietary name.' However, limit is left completely unexplained, including its purpose, default, or constraints, leaving a gap for one of the two parameters.

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 the specific verb 'Find' and clearly identifies the resource: a reference biologic and its FDA-licensed 351(k) products, searched by proper or proprietary name. This distinguishes it from sibling tools like purple_book_biosimilars or purple_book_product_search, which focus on broader listings rather than a reference product and its associated products.

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 the usage scenario (lookup by name for a reference biologic and its 351(k) products) but does not explicitly state when to prefer this tool over alternatives like purple_book_biosimilars or purple_book_product_search. It also provides no exclusions or routing guidance, which is notable given the large sibling set.

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.