Skip to main content
Glama

Ptab Recent Decisions

ptab_recent_decisions
Read-onlyIdempotent

Return and summarize recently issued public PTAB trial decisions, optionally filtered by trial type, patent, or party. Outcome labels describe the document-level USPTO record and require review in proceeding context; they are not claim-by-claim legal conclusions.

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": {
      "days": 90,
      "limit": 25,
      "trial_type": "IPR"
    },
    "name": "ptab_recent_decisions"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNoLook-back window, 1-365 days (default 30).
limitNo1-100, default 25.
partyNo
_apiKeyNoUSPTO ODP API key.
trial_typeNoOptional IPR, PGR, CBM, or DER.
patent_numberNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / days / description
      Previous value: -"Look-back window, 1–365 days (default 30)."New value: +"Look-back window, 1-365 days (default 30)."
    • changedInput schema / properties / limit / description
      Previous value: -"1–100, default 25."New value: +"1-100, default 25."
  2. First observed

TDQS

A3.7/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 genuine value beyond that by disclosing that the tool summarizes results and that outcome labels are document-level USPTO records requiring proceeding context, not claim-by-claim legal conclusions — an important interpretive caveat an agent would otherwise miss. It does not cover volume, rate limits, or pagination behavior.

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?

Two tight sentences, front-loaded with the core action and scope, followed by the interpretive caveat. Nothing is padded, though the second sentence is dense and could be split for readability.

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 six parameters, the description does cover what the tool returns (summarized decisions) and how to read the outcome labels. Remaining gaps — undefined format for party/patent_number and no note on result ordering or truncation beyond limit — are modest for a read-only, optional-parameter list tool.

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 coverage is 67%: days, limit, _apiKey and trial_type are documented in the schema, while party and patent_number are bare names. The description repeats the filter categories without clarifying expected formats for party (name vs. number) or patent_number, so it adds little meaning over the structured fields.

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 pair (return and summarize) and a precise resource ('recently issued public PTAB trial decisions'), with the recency scope made explicit. It implicitly separates itself from the sibling ptab_search_decisions by emphasizing 'recently issued' rather than search, though it never names that alternative directly.

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?

It states the filters available ('optionally filtered by trial type, patent, or party'), which implies when the tool is appropriate, but gives no explicit when-to-use versus when-not guidance and never routes the agent to ptab_search_decisions or ptab_proceeding_timeline for other cases. Usage is inferable rather than stated.

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.