Fda Drug Competition

Orange Book Exclusivity Expirations

orange_book_exclusivity_expirations

Read-onlyIdempotent

When does FDA marketing exclusivity expire for a drug — the listed Orange Book exclusivity expiration dates for a brand or ingredient, with the earliest and latest across the whole schedule. Ask by drug alone to get everything on file; add from_date/to_date only when you want a window, and anything excluded is counted and dated back to you. Exclusivity codes have program-specific meanings; expiration alone does not guarantee generic approval or launch.

Input Schema

TableJSON Schema

Name	Required	Description
`drug`	No	Ingredient, trade name, or applicant, e.g. "Jardiance" or "empagliflozin".
`limit`	No	Results (1-100, default 25).
`to_date`	No	Optional window end YYYY-MM-DD. Omit for the drug's whole schedule.
`from_date`	No	Optional window start YYYY-MM-DD. Omit for the drug's whole schedule.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`source`	Yes
`returned`	Yes
`dataset_note`	No
`dataset_stale`	No
`exclusivities`	Yes
`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"
+}
```

Changed5 schema fields changedAug 11, 2026

changedInput schema / examples

Previous value: -[
-  {
-    "from_date": "2026-01-01",
-    "limit": 25,
-    "to_date": "2028-12-31"
-  }
-]New value: +[
+  {
+    "drug": "Jardiance"
+  },
+  {
+    "from_date": "2026-01-01",
+    "limit": 25,
+    "to_date": "2028-12-31"
+  }
+]

changedInput schema / properties / drug / description

Previous value: -"Optional ingredient, trade name, or applicant."New value: +"Ingredient, trade name, or applicant, e.g. \"Jardiance\" or \"empagliflozin\"."

changedInput schema / properties / from_date / description

Previous value: -"Start YYYY-MM-DD."New value: +"Optional window start YYYY-MM-DD. Omit for the drug's whole schedule."

changedInput schema / properties / to_date / description

Previous value: -"End YYYY-MM-DD."New value: +"Optional window end YYYY-MM-DD. Omit for the drug's whole schedule."

changedInput schema / required

Previous value: -[
-  "from_date",
-  "to_date"
-]New value: +[]

Changed1 schema field changedAug 6, 2026
- changedOutput schema / properties / dataset_updated / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
First observedJul 27, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Beyond the readOnly/idempotent annotations, the description discloses meaningful behavior: it returns earliest/latest dates, counts and dates back excluded items, and warns that expiration alone does not guarantee generic approval or launch. This adds useful context beyond the structured 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 three sentences with no fluff: purpose is front-loaded, usage guidance follows, and a necessary caveat closes it. Every sentence earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read-only query tool with zero required params and an output schema already present, the description covers purpose, parameter usage, and an important interpretation caveat. The only minor flaw is slight ambiguity in 'anything excluded is counted', but overall it is complete enough for an agent to invoke correctly.

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 coverage is 100%, but the description adds semantics beyond the schema by explaining the interaction between drug and date parameters ('Ask by drug alone... add from_date/to_date only when you want a window') and clarifies drug can be brand or ingredient. This elevates it above the baseline 3.

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 clearly states the tool's function: it returns FDA marketing exclusivity expiration dates for a drug, with earliest and latest across the schedule. This specific verb+resource combination distinguishes it from sibling tools like orange_book_patent_expirations.

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 provides clear parameter guidance: ask by drug alone for everything, add from_date/to_date for a window. However, it does not explicitly contrast this tool with alternatives in the sibling list, so it lacks explicit exclusion criteria for when not to use it.

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.