Skip to main content
Glama

search_fda_orange_book_patents

Search FDA Orange Book patent data by drug name, application number, or patent number to retrieve expiry dates, patent flags, and associated exclusivities.

Instructions

Search FDA Orange Book patent data for drug products. Find patents by drug name, application number, or patent number. Returns patent details including expiry dates, substance/product/use flags, and associated exclusivities.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

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

Input Schema

NameRequiredDescriptionDefault
skipNoNumber of results to skip for pagination
limitNoMaximum results to return (1-100, default 10)
applNoNoFDA application number
drugNameNoDrug trade name or ingredient to search
patentNoNoPatent number

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.2.2
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  2. First observedv1.2.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description must carry the full behavioral burden. It usefully discloses what is returned (expiry dates, substance/product/use flags, exclusivities), which signals a read-oriented search, but it does not mention pagination behavior, default limits, permission requirements, or other operational constraints beyond what the input schema already says.

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 two tight sentences: the first establishes purpose, the second summarizes supported lookups and return contents. It is front-loaded and contains no wasted wording.

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?

For a search tool with a fully described schema and no output schema, the description gives sufficient context about search dimensions and return values. It falls short of complete because it does not clarify pagination defaults, whether any filters are required, or how results differ from sibling search tools.

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 five parameters are already explained in the schema. The description restates the three main lookup keys but adds no additional syntax, format, or behavioral detail beyond what the schema provides.

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 states a specific verb and resource: 'Search FDA Orange Book patent data for drug products.' It identifies the supported lookup dimensions (drug name, application number, patent number), making the tool's scope clear, though it does not explicitly differentiate it from closely related siblings like search_fda_orange_book or search_fda_drug_patent_expiry.

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?

Usage is implied by listing the three search strategies (drug name, application number, patent number), but there is no explicit when-to-use guidance, no when-not-to-use guidance, and no named alternative for overlapping patent or Orange Book searches.

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