Skip to main content
Glama
riemannzeta

USPTO Patent MCP Server

by riemannzeta
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

tsdr_download_trademark_documents

Read-onlyIdempotent

Download a trademark’s prosecution document bundle as a base64 PDF, with optional document type and date filters to retrieve office actions, responses, or specimens.

Instructions

Download the prosecution document bundle for a trademark as PDF (base64).

USE THIS TOOL WHEN: You need office actions, responses, specimens, or
other file-wrapper documents for a trademark application.

NOTE: TSDR limits PDF downloads to 4 requests per minute per API key,
and unfiltered full wrappers can exceed 10 MB (rejected with
RESPONSE_TOO_LARGE above 4 MB). Call tsdr_list_trademark_documents
first, then filter by document_type and/or date range.

Args:
    serial_number: 8-digit application serial number (e.g., "78787878")
    document_type: Optional document type filter (e.g., "OOA" for
        outgoing office actions, "SPE" for specimens)
    date_from: Optional start date filter (YYYY-MM-DD)
    date_to: Optional end date filter (YYYY-MM-DD)

Returns:
    Dictionary with base64-encoded PDF data.

Input Schema

NameRequiredDescriptionDefault
date_toNo
date_fromNo
document_typeNo
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_download_trademark_documentsOutput",
-  "type": "object"
-}New value: +null
  2. First observedv1.1.1

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already establish read-only/idempotent/non-destructive, and the description adds real operational constraints on top: a 4-requests-per-minute rate limit, an unfiltered-wrapper size ceiling of ~10 MB, and a hard RESPONSE_TOO_LARGE rejection above 4 MB. That is the kind of behavioral context annotations cannot express.

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?

Well front-loaded: purpose first, then the when-to-use block, then the critical limits, then args. The args/returns sections partially restate the schema, which adds some redundancy, but the operational caveats earn their space.

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?

With no output schema present, the description still tells the agent the return shape ('Dictionary with base64-encoded PDF data') and covers the workflow, rate limit, and size-failure mode. Nothing needed to invoke this correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description carries the full param burden and does so: serial_number is documented as 8-digit with an example ('78787878'), document_type is given concrete filter codes ('OOA', 'SPE'), and both date params specify the YYYY-MM-DD format. Far more than the type-only schema provides.

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?

Opens with a specific verb + resource + output format: 'Download the prosecution document bundle for a trademark as PDF (base64)'. This is clearly distinct from sibling reads like tsdr_list_trademark_documents (list) and tsdr_get_trademark_status (status), so an agent can select it without opening any 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?

An explicit 'USE THIS TOOL WHEN' block names the triggering need (office actions, responses, specimens, file-wrapper documents) and routes the agent through a prerequisite: 'Call tsdr_list_trademark_documents first, then filter by document_type and/or date range.' Both the when and the alternative are stated.

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