Fda Drug Competition

Purple Book Interchangeables

purple_book_interchangeables

Read-onlyIdempotent

List FDA Purple Book products designated 351(k) Interchangeable, optionally filtered by reference product, applicant, or product name. Interchangeability is an FDA designation; pharmacy substitution remains subject to applicable law and circumstances.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`limit`	No
`query`	No

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/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint false, so the safety profile is covered. The description adds a useful caveat about the legal meaning of interchangeability, but does not disclose any additional behavioral details beyond the 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?

Two concise sentences with no filler. The first sentence states the action and scope, and the second adds a necessary regulatory caveat without diluting the core message.

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 output schema and rich annotations, the description covers the core purpose and query semantics adequately. It would be slightly stronger if it explicitly positioned this tool against the related purple_book_* siblings, but nothing essential to invoking it correctly 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?

Schema description coverage is 0%, but the description compensates by explaining that the query can filter by reference product, applicant, or product name. The limit parameter is not described, though its meaning is largely self-evident from the example and parameter name.

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 states a specific action ('List') and a precisely defined resource ('FDA Purple Book products designated 351(k) Interchangeable'). It clearly distinguishes this from sibling tools like purple_book_biosimilars by foregrounding the interchangeability designation.

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 explains optional filtering by reference product, applicant, or product name, which gives some usage context. However, it does not explicitly state when to choose this tool over related sibling tools such as purple_book_biosimilars, purple_book_product_search, or purple_book_reference_product.

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.