Skip to main content
Glama

Ptab Search Interferences

ptab_search_interferences
Read-onlyIdempotent

Search USPTO patent Interference decisions, pre-AIA priority contests between competing applicants/patentees over who invented first. A SEPARATE docket from AIA trials and ex parte Appeals. Filter by patent_number (a patent or application involved in the contest), party (junior- or senior-party name, or either party's real party in interest), and/or free-text query. Returns the interference number, style ("A v. B"), declaration date, the junior and senior party (each with name, real party in interest, inventor, counsel, application/patent number, grant date), any additional parties, decision type/date and outcome, and the decision document 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": {
      "patent_number": "9876543"
    },
    "name": "ptab_search_interferences"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoNumber of results (1-100, default 25).
partyNoOptional. Junior- or senior-party name in the priority contest.
queryNoOptional free-text keyword search across interference decision records.
offsetNoPagination offset (default 0).
_apiKeyNoUSPTO ODP API key.
include_rawNoOptional, default false. When true, also return raw_sample: one UNMODIFIED raw record exactly as the upstream API returned it (no field renaming), to verify or correct this tool's field mapping.
patent_numberNoOptional. Patent or application number involved in the interference.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, open-world, so the safety profile is covered. The description adds domain behavior the annotations cannot: this is a pre-AIA interference docket, sourced from data.uspto.gov, and it enumerates what a record contains (party structure, decision type/outcome, document link). It does not discuss result caps or pagination behavior, which the schema handles instead.

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-loads what the docket is, then filters, then return shape, then data source, which is the right order. The field enumeration is long but justified because there is no output schema; only mild compression is possible.

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 correctly compensates by listing returned fields, and it covers filters, domain scope, and upstream source for a 7-parameter tool. Minor gaps: no mention of API-key/auth requirement or result-size expectations, though the schema documents `_apiKey` and `limit`.

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 the baseline is 3. The description adds modest nuance — that `patent_number` may be a patent or application and that `party` reaches real parties in interest, not just named parties — but it does not explain `query` syntax, `limit`/`offset` behavior, or `include_raw` beyond what the schema states.

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?

Uses a specific verb and resource ('Search USPTO patent Interference decisions') and immediately scopes the domain as pre-AIA priority contests. It explicitly distinguishes itself from adjacent dockets ('A SEPARATE docket from AIA trials and ex parte Appeals'), so an agent can tell it apart from ptab_search_decisions/appeals without opening a 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 'SEPARATE docket' sentence gives clear selection context versus AIA-trial and appeal tools, and the filter list implies the intended query patterns. It stops short of explicit when-not-to-use exclusions or naming a specific sibling, but the routing signal is unambiguous.

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.