Skip to main content
Glama
riemannzeta

USPTO Patent MCP Server

by riemannzeta

tsdr_download_trademark_documents

Download trademark prosecution documents, such as office actions and specimens, as a PDF. Filter by document type or date range to keep downloads within size limits.

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

TableJSON Schema
NameRequiredDescriptionDefault
date_toNo
date_fromNo
document_typeNo
serial_numberYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

With no annotations, the description fully discloses rate limits (4/min), size limits (10 MB, rejected above 4 MB with RESPONSE_TOO_LARGE), and the required prefiltering step. It also mentions the base64 PDF return format, covering the key behavioral aspects the agent needs to know.

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?

The description is front-loaded with the core purpose, then usage guidance, constraints, and parameter details in logical order. Every sentence serves a purpose—no filler, and the structure aids quick comprehension.

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?

Given the tool's complexity (4 params, 1 required) and no annotations, the description is comprehensive: it explains output (base64 PDF), required pre-step (list), constraints (rate/size), and parameter specifics. It fully equips the agent to use the tool correctly.

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 coverage is 0%, so the description must fill the gap. It does: serial_number format (8-digit) with example, document_type with concrete examples (OOA, SPE), and date range formats (YYYY-MM-DD). This adds substantial meaning beyond the raw schema.

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?

The description clearly states the action: 'Download the prosecution document bundle for a trademark as PDF (base64)' and specifies content types (office actions, responses, specimens). This verb+resource structure distinguishes it from siblings like tsdr_list_trademark_documents and tsdr_get_trademark_image by focusing on downloading documents.

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?

It explicitly says 'USE THIS TOOL WHEN' and lists the use cases, then advises calling tsdr_list_trademark_documents first and filtering. This provides clear context and workflow direction, effectively differentiating from alternatives.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/riemannzeta/patent_mcp_server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server