Skip to main content
Glama
riemannzeta

USPTO Patent MCP Server

by riemannzeta

ptab_search_appeals

Locate ex parte appeal decisions from the Patent Trial and Appeal Board using full-text queries, patent or application numbers, and decision date filters to find specific rulings.

Instructions

Search ex parte appeal decisions. Live via USPTO ODP v3.0.

Args:
    query: Full-text search query
    application_number: Filter by application 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
patent_numberNo
decision_date_toNo
application_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?

With no annotations provided, the description must disclose behavioral traits. It only mentions 'Live via USPTO ODP v3.0', implying a live data source, but does not describe output format, pagination behavior, rate limits, or any side effects. This is inadequate for a search tool.

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 highly concise: one purpose sentence followed by a parameter list. There is no unnecessary prose, and the most important information (purpose) is front-loaded. This is an efficient use of space.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool has 7 optional parameters and an output schema (which is not provided but noted). The description covers the purpose and parameters but lacks context on what constitutes an 'ex parte appeal decision' or how this search differs from sibling searches. Given the output schema exists, the description is minimally adequate but not comprehensive.

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 coverage is 0%, so the description's parameter list is essential. Each parameter has a short semantic comment (e.g., 'Full-text search query', 'Filter by application number'), which adds meaning beyond the schema's plain types and defaults, effectively compensating for the lack of schema 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?

The description states 'Search ex parte appeal decisions' which is a clear verb+resource combination. It clearly identifies the tool's purpose but does not explicitly differentiate from sibling tools like ptab_search_decisions, though the specificity of 'ex parte appeal' provides some distinction.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives. It mentions 'Live via USPTO ODP v3.0' which gives a data source context but no exclusions or alternative tool suggestions, leaving the agent without clear usage direction.

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