Skip to main content
Glama

Ptab Appeal

ptab_appeal
Read-onlyIdempotent

Get one USPTO ex parte Appeal decision by its appeal number (e.g. "2024-001234"), the Board's decision on an applicant's appeal of an examiner rejection. Returns the decision type, issue date, outcome (affirmed / reversed / affirmed-in-part), issues and rules at play, and the decision document title + download link. 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": {
      "appeal_number": "2024-001234"
    },
    "name": "ptab_appeal"
  }
}

Input Schema

NameRequiredDescriptionDefault
_apiKeyNoUSPTO ODP API key.
include_rawNoOptional, default false. When true, also return raw_sample: the UNMODIFIED raw record exactly as the upstream API returned it (no field renaming), to verify or correct this tool's field mapping.
appeal_numberYesEx parte appeal number, e.g. "2024-001234" (with or without an "Appeal" prefix).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already establish readOnly, idempotent, open-world, non-destructive behavior, so the description is not carrying the safety burden. It adds useful context about the returned content and provenance (USPTO Open Data Portal), but says nothing about not-found behavior, rate limits, or API key requirements beyond the schema.

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 front-loaded sentences: identity/scope first, then the returned fields. The repeated '2024-001234' example duplicates the schema example, a minor redundancy, but there is no filler.

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, the description does the work of enumerating return fields (decision type, issue date, outcome, issues/rules, document title and link), which is exactly what an agent needs to decide this tool answers its question. Only error and edge-case behavior is missing.

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 100%, so all three parameters including _apiKey and include_raw are already documented in structured form. The description's example format restates what the schema says and adds no new syntactic or semantic guidance, so the baseline of 3 applies.

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+resource: retrieve one ex parte Appeal decision by appeal number, and clarifies the domain (Board decision on an applicant's appeal of an examiner rejection). The singular, ID-based scope implicitly separates it from the ptab_search_appeals sibling, but no sibling is named explicitly.

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 by the input contract (you must already have an appeal number), and the description clarifies what kind of record you get back. It never states when to use this instead of ptab_search_appeals (e.g., when you don't have a number yet) or what happens for an unknown number.

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.