Skip to main content
Glama

Ptab Search Documents

ptab_search_documents
Read-onlyIdempotent

Search USPTO PTAB filings and documents within trial proceedings, petitions, patent-owner responses, expert declarations, exhibits, motions, and briefs. Pass proceeding_number (the trial number, e.g. "IPR2024-00001") to list every document filed in a proceeding, and/or query for free-text search. Returns document name/title, type, filing date, filing party, size, and download URI. Powered by the USPTO Open Data Portal (data.uspto.gov).

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": {
      "proceeding_number": "IPR2024-00001"
    },
    "name": "ptab_search_documents"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoNumber of results (1-100, default 25).
queryNoOptional free-text keyword search across document records (e.g. "declaration", "petition"). Combined with proceeding_number via AND.
offsetNoPagination offset (default 0).
_apiKeyNoUSPTO ODP API key (same key as the patents pack). Get free at https://data.uspto.gov/apis/getting-started.
proceeding_numberNoTrial/proceeding number to list documents for, e.g. "IPR2024-00001", "PGR2026-00039". Matches trialNumber.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld, and non-destructive, so the safety profile is covered. The description adds useful behavioral context: it returns document name/title, type, filing date, filing party, size and download URI, and that proceeding_number lists all filings. It does not discuss pagination behavior or rate limits.

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 front-loaded sentences: purpose, parameter usage, and return fields. No filler; the brief source attribution is useful rather than padding.

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 no-required-parameter search tool with no output schema, the description covers purpose, usage, and return fields. Pagination and result-ordering behavior are left to the schema's limit/offset descriptions, which is a minor gap.

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 documented in the schema. The description reinforces proceeding_number and query examples and the AND combination, but adds little semantic detail beyond the structured field descriptions.

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?

States a specific verb ('Search') and resource ('USPTO PTAB filings and documents') and enumerates document types, so an agent knows this is document-level search. It does not explicitly name sibling tools like ptab_search_proceedings or ptab_search_decisions to distinguish scope, so not a 5.

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?

Explains that proceeding_number lists every document in a proceeding and query adds free-text search, and the schema notes the AND combination. However, it gives no when-not guidance or explicit alternatives among the sibling PTAB search tools.

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.