Skip to main content
Glama
riemannzeta

USPTO Patent MCP Server

by riemannzeta
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

tsdr_list_trademark_documents

Read-onlyIdempotent

List prosecution document metadata for a trademark application without downloading PDFs; returns document type codes, descriptions, and dates for file-wrapper review.

Instructions

List prosecution document metadata for a trademark (no downloads).

USE THIS TOOL WHEN: You want to see what file-wrapper documents exist
for a trademark application (office actions, responses, specimens,
registration certificates) before downloading anything. Unlike
tsdr_download_trademark_documents, this returns metadata only and is
NOT subject to the 4 req/min PDF rate limit. Use the DocumentTypeCode
values it returns (e.g. "OOA", "SPE") as the document_type filter when
downloading.

Args:
    serial_number: 8-digit application serial number (e.g., "78787878")

Returns:
    Document metadata records (type, description, dates).

Input Schema

NameRequiredDescriptionDefault
serial_numberYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.8.1
    • changedOutput schema / (root)
      Previous value: -{
-  "properties": {
-    "result": {
-      "additionalProperties": true,
-      "title": "Result",
-      "type": "object"
-    }
-  },
-  "required": [
-    "result"
-  ],
-  "title": "tsdr_list_trademark_documentsOutput",
-  "type": "object"
-}New value: +null
  2. First observedv1.1.1

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive. The description adds genuinely non-obvious context: metadata only, no downloads, and critically that it is NOT subject to the 4 req/min PDF rate limit that constrains the sibling. Pagination behavior is not stated, keeping it short of a 5.

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?

Front-loaded with purpose, then a clearly delineated usage block, args, and returns. Every sentence carries information; nothing is padding for a tool of this simplicity.

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

Completeness5/5

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

For a read-only metadata list with one required param, the description covers purpose, routing, rate-limit caveat, parameter format, and the shape of the return ('type, description, dates') despite the absence of an output schema. Nothing an agent needs to call it correctly is missing.

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% and the single parameter is undocumented in the schema, so the description must carry the load. It does: format ('8-digit application serial number') plus a concrete example ('78787878'), which is what an agent needs to invoke correctly.

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 ('List prosecution document metadata for a trademark') and immediately scopes it with '(no downloads)'. This distinguishes it cleanly from the sibling tsdr_download_trademark_documents without requiring the agent to open either schema.

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

Usage Guidelines5/5

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

Explicit 'USE THIS TOOL WHEN' section names the exact scenario (see what file-wrapper documents exist before downloading) and names the alternative tool it is not. It further explains how its output feeds the download tool's document_type filter, closing the loop between the two tools.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools