Skip to main content
Glama

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.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "drug": "Jardiance"
    },
    "name": "orange_book_exclusivity_expirations"
  }
}

Input Schema

NameRequiredDescriptionDefault
drugNoIngredient, trade name, or applicant, e.g. "Jardiance" or "empagliflozin".
limitNoResults (1-100, default 25).
to_dateNoOptional window end YYYY-MM-DD. Omit for the drug's whole schedule.
from_dateNoOptional window start YYYY-MM-DD. Omit for the drug's whole schedule.

Output Schema

NameRequiredDescriptionDefault
sourceYes
returnedYes
dataset_noteNo
dataset_staleNo
exclusivitiesYes
dataset_updatedNo
dataset_age_daysNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • 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"
      +}
  2. Changed5 schema fields changed
    • 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: +[]
  3. Changed1 schema field changed
    • changedOutput schema / properties / dataset_updated / type
      Previous value: -"string"New value: +[
      +  "string",
      +  "null"
      +]
  4. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Beyond the readOnly/idempotent annotations, the description discloses truncation behavior ('anything excluded is counted and dated back to you') and an important interpretive caveat that exclusivity codes are program-specific and expiration does not guarantee generic approval or launch. That is substantive domain context an agent cannot get from the structured fields.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the core question the tool answers, then invocation guidance, then caveats — a sensible ordering with no filler sentences. The opening clause is grammatically fragmentary, which slightly slows parsing but does not waste space.

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 an output schema present, return-shape detail is rightly omitted, and the description covers default mode, windowing, truncation reporting, and the interpretive limit on codes. What remains thin is how this tool relates to the sibling patent and loss-of-exclusivity tools, which matters for an agent choosing among them.

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?

Schema description coverage is 100%, so all four parameters are already documented; the description only restates the optional-window semantics for from_date/to_date and omits the 'drug' identifier breadth and the 1-100 limit range. Baseline 3 is appropriate since the schema carries the parameter load.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb-and-resource pair (FDA marketing exclusivity expiration dates from the Orange Book) with scope detail: brand or ingredient, earliest/latest across the whole schedule. The resource framing implicitly separates it from orange_book_patent_expirations, but it never states the distinction explicitly, so an agent must infer it from the noun.

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?

'Ask by drug alone to get everything on file; add from_date/to_date only when you want a window' gives clear default-mode versus filtered-mode guidance, which is the main invocation decision here. It stops short of naming alternatives (e.g. patent expirations or the loss-of-exclusivity profile), so there is no explicit when-not or sibling routing.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.