Skip to main content
Glama
riemannzeta

USPTO Patent MCP Server

by riemannzeta

ptab_search_decisions

Search PTAB trial decisions by full-text query, decision type, proceeding or patent number, and decision date range. Find relevant patent trial outcomes quickly.

Instructions

Search PTAB trial decisions. Live via USPTO ODP v3.0.

Args:
    query: Full-text search in decision text
    decision_type: Type (institution, final, termination)
    proceeding_number: Filter by proceeding number
    patent_number: Filter by patent number
    decision_date_from: Date range start (YYYY-MM-DD)
    decision_date_to: Date range end (YYYY-MM-DD)
    offset: Starting position (default: 0)
    limit: Max results (default: 25)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo
queryNo
offsetNo
decision_typeNo
patent_numberNo
decision_date_toNo
proceeding_numberNo
decision_date_fromNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior2/5

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

No annotations are provided, so the description must fully disclose behavioral traits. It mentions 'Live via USPTO ODP v3.0' but does not state that the operation is read-only, describe pagination behavior, or note any rate limits or side effects. The search nature implies safety, but the description carries the burden and under-delivers.

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 a well-structured docstring with a one-sentence summary followed by a compact Args list. Every line provides essential information, with no fluff or redundancy. It is front-loaded with the core purpose and effectively organizes parameter details.

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?

Given the presence of an output schema, return values need not be described. The description covers all 8 parameters and provides useful context such as defaults and live data source. However, it omits details about how filters combine (AND/OR), whether date bounds are inclusive, or if there is a maximum limit, which would enhance completeness for a search tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description provides a clear one-line semantic for each of the 8 parameters, including the full-text search behavior of 'query', valid values for 'decision_type', and date formats. Since the input schema only lists titles and types with zero description coverage, the description fully compensates and adds significant meaning.

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 begins with 'Search PTAB trial decisions,' which is a specific verb+resource statement that clearly identifies the tool's function. It distinguishes itself from sibling tools like ptab_search_proceedings and ptab_search_appeals by explicitly focusing on decisions, and the name 'ptab_search_decisions' reinforces this.

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 use for searching trial decisions but does not explicitly state when to use this tool versus related tools like ptab_get_decision or ptab_search_proceedings. There is no mention of exclusions or when to prefer alternatives, so the guidance is clear but implicit.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/riemannzeta/patent_mcp_server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server