Skip to main content
Glama

Ptab Search Decisions

ptab_search_decisions
Read-onlyIdempotent

Search USPTO PTAB decision documents, institution decisions and final written decisions issued in IPR/PGR/CBM trials, plus appeal outcomes. Returns the trial number, decision type, issue date, trial/appeal outcome, the issue types and statutes/rules at play, and the decision document title + download URI. Filter by free-text query, patent_number, trial_type, and a decided_after/decided_before date range. 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",
      "decided_after": "2023-01-01",
      "patent_number": "12018298"
    },
    "name": "ptab_search_decisions"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoNumber of results (1-100, default 10).
queryNoOptional free-text keyword search across decision records.
offsetNoPagination offset (default 0).
_apiKeyNoUSPTO ODP API key (same key as the patents pack). Get free at https://data.uspto.gov/apis/getting-started.
trial_typeNoOptional. Trial type code: IPR, PGR, CBM, DER. Matches trialMetaData.trialTypeCode.
decided_afterNoOptional. Only decisions on/after this date (ISO YYYY-MM-DD). Matches trialMetaData.latestDecisionDate.
patent_numberNoOptional. Challenged patent number, e.g. "12018298". Matches patentOwnerData.patentNumber.
decided_beforeNoOptional. Only decisions on/before this date (ISO YYYY-MM-DD). Matches trialMetaData.latestDecisionDate.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered without help from the description. The description adds genuine context the annotations cannot: the upstream source (USPTO Open Data Portal) and the exact fields returned, which matters because there is no output schema. It says nothing about rate limits, result caps, or how the upstream source behaves when unavailable.

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?

Three sentences, front-loaded with what the tool searches, then return fields, then filters, then provenance. Every clause carries information. The return-field enumeration is dense but justified given the absence of an output schema; only the trailing 'Powered by the USPTO Open Data Portal' is nearly 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 read-only, zero-required-parameter search tool with no output schema, the description covers the essentials: what corpus is searched, what comes back, and which filters exist. The API key requirement is handled in the schema rather than the description, which is reasonable. The one real gap is disambiguation from the crowded PTAB search sibling set.

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%, including the trial_type enum values, ISO date formats, and even the underlying API field mappings, so the schema already carries the semantics. The description's filter sentence largely restates those same parameters (query, patent_number, trial_type, decided_after/decided_before) without adding format, defaulting, or matching behavior beyond what the schema documents.

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 and resource (search USPTO PTAB decision documents) and enumerates the document families covered — institution decisions, final written decisions in IPR/PGR/CBM, and appeal outcomes. That is far more than a restatement of the name. It does not, however, distinguish itself from near-identical siblings such as ptab_search_documents, ptab_recent_decisions, or ptab_search_appeals, which the 'plus appeal outcomes' clause arguably overlaps with.

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 through the enumerated filter set (query, patent_number, trial_type, date range) and worked examples, so an agent can infer typical call shapes. There is no explicit 'use this when…' or 'prefer X instead' guidance, and no statement about when this tool is the wrong choice relative to the several PTAB search siblings.

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.