Skip to main content
Glama

Ttab Search

ttab_search
Read-onlyIdempotent

Searches USPTO Trademark Trial and Appeal Board (TTAB) proceedings, trademark oppositions, cancellation petitions, extensions of time to oppose, and ex parte appeals, by party name, mark text, correspondent law firm, or application/registration number. Answers "is anyone opposing this trademark", "who has petitioned to cancel this registration", "which brands does this company fight", "what TTAB disputes involve this mark". Each result carries the board proceeding number, proceeding type (opposition, cancellation, extension of time, ex parte appeal), filing date, and both sides, defendant and plaintiff, each with their marks and serial/registration numbers. 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": {
      "limit": 5,
      "party": "Nike, Inc."
    },
    "name": "ttab_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
markNoTrademark text being fought over, e.g. "JUST DO IT".
pageNo1-based page; TTABVUE returns 25 proceedings per page, newest first.
limitNoMax proceedings to return from the page, 1-25. Default 25.
partyNoParty name as filed, e.g. "Nike, Inc." or just "Nike". Matches either side of the proceeding.
queryNoAll these words anywhere in the record, proceeding number, application/registration number, parties, or marks.
statusNoProceeding status filter. Default all.
match_modeNoHow party/mark/correspondent text is matched. Default contains.
other_partyNoSecond party name, use with `party` to find proceedings between two specific companies.
correspondentNoCorrespondent (law firm or attorney of record) name.
serial_or_registration_numberNoApplication serial number, registration number, or expungement/reexamination number the proceeding is about.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / other_party / description
      Previous value: -"Second party name — use with `party` to find proceedings between two specific companies."New value: +"Second party name, use with `party` to find proceedings between two specific companies."
    • changedInput schema / properties / query / description
      Previous value: -"All these words anywhere in the record — proceeding number, application/registration number, parties, or marks."New value: +"All these words anywhere in the record, proceeding number, application/registration number, parties, or marks."
  2. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld, non-destructive, so the safety profile is covered. The description adds useful context beyond that: the live USPTO TTABVUE source and the exact fields each result carries (proceeding number, type, filing date, both sides with marks and numbers).

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?

Front-loaded with the core verb and resource, then useful example queries. The first sentence is long and list-heavy but each element (proceeding types, search keys) earns its place; nothing is redundant.

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 compensates by describing the return fields in detail, which is the right call for a 10-parameter search tool. Minor gap: no note on result volume or behavior at page boundaries beyond what the schema states.

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 each of the 10 parameters is documented in-schema, including pagination, match modes and enum values. The description adds no parameter-level detail beyond the schema, so the baseline 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?

Specific verb ('Searches') plus resource (USPTO TTAB proceedings) with an enumeration of proceeding types (opposition, cancellation, extension of time, ex parte appeal) and searchable keys. It does not name or differentiate against siblings like ttab_party_history or ttab_proceeding, which keeps it from a 5.

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 ('is anyone opposing this trademark', 'which brands does this company fight') give clear situational context for when to reach for this tool. There is no explicit when-not guidance or named alternative, so it falls short of a 5.

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.