Fda Drug Competition

Orange Book Expiry Cliff Calendar

orange_book_expiry_cliff_calendar

Read-onlyIdempotent

Create a combined calendar of FDA Orange Book patent and regulatory-exclusivity expirations. Returns dated events with ingredient, trade name, applicant, application, patent/use-code, and exclusivity-code context for cliff monitoring.

Input Schema

TableJSON Schema

Name	Required	Description
`drug`	No	Optional ingredient, trade name, or applicant filter.
`limit`	No	Events (1-100, default 50).
`to_date`	Yes
`from_date`	Yes
`event_type`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`events`	Yes
`source`	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"
+}
```
AddedAug 6, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already disclose read-only, idempotent, non-destructive behavior. The description adds that the tool returns dated events with ingredient, trade name, applicant, application, patent/use-code, and exclusivity-code context, which is useful beyond the schema. It omits minor details like limit clamping or event_type filtering, but the annotation coverage lowers the burden.

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 core action is front-loaded and the return-value context is summarized efficiently.

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?

With read-only annotations and an output schema present, the description provides enough context for an agent to understand the tool's purpose and output. Date format is demonstrated in the schema example, and event_type is enumerable. Minor gaps around filtering behavior exist but do not block correct invocation.

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

Parameters2/5

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

Schema description coverage is only 40%, and the description does not compensate. from_date and to_date have no schema descriptions and the description does not explain date range semantics or event_type filtering. It only implicitly references patent and exclusivity event types.

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 and resource: it creates a combined calendar of Orange Book patent and regulatory-exclusivity expirations. By emphasizing 'combined,' it clearly differentiates this tool from sibling tools like orange_book_patent_expirations and orange_book_exclusivity_expirations.

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 phrase 'combined calendar' and 'cliff monitoring' imply usage for a broad patent/exclusivity expiration view, but the description does not explicitly say when to prefer this tool over dedicated patent-only or exclusivity-only siblings. Usage guidance is present by implication, not by direct contrast.

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.