Skip to main content
Glama
riemannzeta

USPTO Patent MCP Server

by riemannzeta

tsdr_list_trademark_documents

List trademark application file-wrapper document metadata to see available office actions, responses, and specimens before downloading. Returns document types, descriptions, and dates for any serial number.

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

TableJSON Schema
NameRequiredDescriptionDefault
serial_numberYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It clearly states the operation is metadata-only, performs no downloads, and is not subject to the 4 req/min PDF rate limit, which is valuable non-obvious behavior. However, it does not mention auth requirements, other rate limits, or error handling, though for a simple read-only list that is a minor gap.

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?

The description is well-structured with a one-line summary, a use-case paragraph, and Args/Returns sections. It is front-loaded with the key purpose. Slight redundancy exists (e.g., 'metadata only' appears multiple times), but every sentence contributes functional guidance, making it appropriately concise.

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 single-parameter metadata listing tool with an output schema, the description covers the purpose, usage context, parameter format, return value, and integration with the download sibling. It does not leave critical operational gaps, making it complete for the agent's decision-making.

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?

The only parameter, serial_number, is given an explicit format ('8-digit') and an example ('78787878') in the description, while the schema provides no description for it. This fully compensates for the 0% schema description coverage, giving the agent precise guidance on how to fill the parameter.

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 opens with a specific verb+resource phrase: 'List prosecution document metadata for a trademark (no downloads).' It clearly distinguishes itself from the sibling tdrs_download_trademark_documents by explicitly stating it returns metadata only and excludes downloads.

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 contains an explicit 'USE THIS TOOL WHEN' section that tells the agent to use it to see what file-wrapper documents exist before downloading. It directly names the alternative tool tdrs_download_trademark_documents and explains the rate-limit difference, plus how to feed DocumentTypeCode values into the download tool's filter.

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