Skip to main content
Glama

Ttab Proceeding

ttab_proceeding
Read-onlyIdempotent

Returns one USPTO TTAB proceeding in full: its type (opposition, cancellation, extension of time to oppose, ex parte appeal), status and status date, filing date, interlocutory attorney and paralegal, both parties with their correspondence addresses and every pleaded mark (serial number, registration number, application status), and the complete prosecution history, every docket entry with its date, text, and any due date. Answers "what happened in TTAB proceeding 91308065", "is this opposition still pending", "what is the answer deadline", "which marks were pleaded". Sourced live from USPTO TTABVUE.

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": {
      "proceeding_number": "91308065"
    },
    "name": "ttab_proceeding"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNoProceeding type. Only needed to disambiguate an extension of time (EXT) from an ex parte appeal (EXA), which share the application serial-number space.
proceeding_numberYes8-digit board proceeding number (91xxxxxx opposition, 92xxxxxx cancellation), or the application serial number for an extension of time / ex parte appeal.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already cover readOnly, idempotent, openWorld, and non-destructive, so the safety profile is settled. The description adds genuinely useful context the annotations cannot: the data is sourced live from USPTO TTABVUE and the response includes the complete prosecution history and every docket entry with due dates, which tells the agent to expect a potentially large, authoritative payload.

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?

The payload contents are front-loaded in a single dense sentence, followed by compact example queries and a provenance line, with no filler. The opening sentence is long and list-heavy, which slightly hurts scanability, but every clause carries information.

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 carries the return-value burden and does so thoroughly, covering entity fields, marks, and docket history, plus the data source. The only gaps are operational edge cases such as behavior for an unknown proceeding number or handling of very large dockets.

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%, and the enum and the EXT/EXA disambiguation rule are already fully documented in the schema. The description adds no syntax, format, or edge-case detail about proceeding_number or type beyond what the schema provides, so the baseline of 3 applies.

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?

States a specific verb and resource ('Returns one USPTO TTAB proceeding in full') and then enumerates exactly what 'full' means: type, status, dates, parties, pleaded marks, prosecution history, and docket entries. This is far beyond restating the name and lets an agent distinguish it from ttab_search (lookup) or ttab_party_history (party-centric) without opening the schema.

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

Usage Guidelines4/5

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

The example questions ('what happened in TTAB proceeding 91308065', 'is this opposition still pending', 'what is the answer deadline') make the use case concrete and imply when to reach for this tool. There is no explicit exclusion or named alternative for related lookups, so the routing guidance is clear but not complete.

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.