Fda Drug Competition

Orange Book Patent Expirations

orange_book_patent_expirations

Read-onlyIdempotent

When do the patents on a drug expire — the listed Orange Book patent expiration dates for a brand or ingredient, in order, with the earliest and latest across the whole schedule. Ask by drug alone ("Xarelto", "semaglutide") to get its full expiry schedule; add from_date/to_date only when you actually want a window, and anything the window excludes is counted and dated back to you so a filtered view is never mistaken for the full picture. Covers small-molecule drugs; biologics are in the Purple Book. Dates are sponsor-submitted FDA listings and do not establish freedom to operate or a certain launch date.

Input Schema

TableJSON Schema

Name	Required	Description
`drug`	No	Ingredient, trade name, or applicant, e.g. "Xarelto" or "rivaroxaban".
`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
`patents`	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"
+}
```

Changed5 schema fields changedAug 11, 2026

changedInput schema / examples

Previous value: -[
-  {
-    "drug": "apixaban",
-    "from_date": "2026-01-01",
-    "limit": 25,
-    "to_date": "2028-12-31"
-  }
-]New value: +[
+  {
+    "drug": "Xarelto"
+  },
+  {
+    "drug": "Ozempic",
+    "limit": 100
+  },
+  {
+    "drug": "apixaban",
+    "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. \"Xarelto\" or \"rivaroxaban\"."

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

Behavior5/5

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

Beyond the readOnly/openWorld/idempotent annotations, the description reveals the exclusion-counting behavior: anything the date window excludes is counted and dated back so a filtered view is not mistaken for the full picture. It also discloses that FDA listings are sponsor-submitted and do not establish freedom to operate or launch date, adding meaningful caveats beyond annotation-provided hints.

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?

Three dense sentences, each earning its place: purpose and ordering in the first, usage guidance in the second, and scope/caveats in the third. The content is front-loaded and free of filler.

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?

With an output schema present, return values are already covered. The description supplies the remaining context an agent needs: what the tool does, when to use it, the small-molecule vs biologic boundary, filter semantics, and important data limitations. No critical information 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 coverage is 100%, so the baseline is 3. The description adds value by clarifying that drug alone returns the full schedule, that from_date/to_date create a window, and that excluded results are still reported. Limit is not discussed in the description, but the schema fully documents it, so this is not a major gap.

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 verb and resource: it returns Orange Book patent expiration dates for a drug, organized in order with earliest and latest across the schedule. It also distinguishes itself from Purple Book biologics tools, which is enough to separate it from sibling tools like orange_book_exclusivity_expirations and purple_book_biosimilars.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives explicit when-to-use guidance: ask by drug alone for a full schedule, add from_date/to_date only for a window, and notes that biologics belong in the Purple Book. This tells the agent when to use this tool versus alternatives, including a pointer to a different resource.

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.