Skip to main content
Glama

Ptab Search Proceedings

ptab_search_proceedings
Read-onlyIdempotent

Search USPTO PTAB trial proceedings, patent litigation before the Patent Trial and Appeal Board (inter partes review / IPR, post-grant review / PGR, covered-business-method / CBM, derivation). Returns trial number, type, status, the challenged patent, petitioner, patent owner, and key dates (petition filing, institution decision, latest decision, termination). Filter by free-text query, patent_number (the patent being challenged), party (petitioner or patent-owner real-party name), trial_type (IPR/PGR/CBM/DER), and/or status. 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": {
      "trial_type": "IPR",
      "patent_number": "11809431"
    },
    "name": "ptab_search_proceedings"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoNumber of results (1-100, default 10).
partyNoOptional. Petitioner or patent-owner real-party-in-interest name, e.g. "Apple" or "Zydus Lifesciences". Matches either regularPetitionerData or patentOwnerData real-party name.
queryNoOptional free-text keyword search across the proceeding record (e.g. a technology term or company name). Combined with the structured filters below via AND.
offsetNoPagination offset (default 0).
statusNoOptional. Trial status category, e.g. "Pending", "Terminated", "Final Written Decision", "Instituted". Matches trialMetaData.trialStatusCategory.
_apiKeyNoUSPTO ODP API key (same key as the patents pack). Get free at https://data.uspto.gov/apis/getting-started. Falls back to platform key if configured.
trial_typeNoOptional. Trial type code: IPR (inter partes review), PGR (post-grant review), CBM (covered business method), DER (derivation). Matches trialMetaData.trialTypeCode.
patent_numberNoOptional. Patent number under challenge, e.g. "11809431" or "US9876543B2". Matches patentOwnerData.patentNumber.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

The annotations already declare readOnly, idempotent, open-world, and non-destructive behavior, so the safety profile is covered. The description adds genuinely useful context beyond that: the upstream data source (USPTO Open Data Portal), the exact return fields (trial number, type, status, challenged patent, parties, key dates), and that query combines with structured filters via AND. It omits rate limits and pagination caps beyond the limit/offset parameters, which keeps it below 5.

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 sentences: the first front-loads purpose, scope, and return shape; the second enumerates filters and the data source. Every clause carries information, and nothing is repeated from the annotations or schema verbatim.

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 no output schema and eight optional parameters, the description carries a fair share of the load and does so by listing the return fields and the filter semantics. It is close to complete, though it does not state default result volume or how pagination should be driven, which an agent must infer from limit/offset.

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 description coverage is 100%, so the baseline is 3, but the description adds meaning on top of it: it clarifies that patent_number refers to the patent being challenged, that party spans petitioner or patent owner, and that query is ANDed with structured filters. It also maps parameters to their underlying record paths (e.g., trialMetaData.trialTypeCode), which helps the agent reason about matching semantics.

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 gives a specific verb and resource ("Search USPTO PTAB trial proceedings") and pins down the domain by enumerating the trial types it covers (IPR, PGR, CBM, derivation). That enumeration separates it from sibling tools like ptab_search_appeals, ptab_search_decisions, and ptab_search_interferences without the agent needing to open a schema.

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 description implies when to use it by defining the resource narrowly and by describing exclusion-free filtering with query, patent_number, party, trial_type, and status. But there is no explicit guidance on choosing this tool over siblings, and no stated prerequisites or exclusions. Usage is inferable from scope alone, which is the definition of a 3.

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.