Skip to main content
Glama
Sign In
USPTO Patent MCP Server

USPTO Patent MCP Server

by riemannzeta
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

ppubs_download_patent_pdf

Read-onlyIdempotent

Download a patent's official PDF document as base64-encoded data by supplying its patent number, enabling offline retrieval and review.

Instructions

Download a patent as PDF (base64 encoded).

USE THIS TOOL WHEN: You need the official PDF document of a patent.
Note: Claude Desktop may not fully support PDF display.

Args:
    patent_number: Patent number ("7123456", "US 10,000,000 B2",
           "D845123" and "RE49123" all work).

Returns:
    Dictionary with base64-encoded PDF data.

Input Schema

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

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent and non-destructive behavior, so the bar is lower; the description still adds real context by disclosing the base64 payload format and warning that Claude Desktop may not fully support PDF display. It omits anything about size limits or failure modes for invalid patent numbers.

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-loaded with the core action, then a short usage line, args, and return shape; every section earns its place. The "Args:"/"Returns:" scaffolding is slightly boilerplate-heavy for one parameter but not wasteful.

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 describes the return value (dictionary with base64 PDF data) and flags the client-side display caveat that an agent would otherwise discover only by failing. Failure behavior for an unresolvable patent number is the remaining gap.

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 description coverage is 0% for the single parameter, so the description carries the burden, and it does so with concrete accepted formats ("7123456", "US 10,000,000 B2", "D845123", "RE49123"). That materially reduces trial-and-error, though it doesn't state whether non-US or application numbers are accepted.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (Download) plus resource (patent PDF) and the encoding (base64), which is enough for an agent to know exactly what it gets. It does not explicitly distinguish itself from near-siblings like ppubs_get_full_document or ppubs_get_patent_by_number, so it stops short of a 5.

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?

"USE THIS TOOL WHEN: You need the official PDF document of a patent" gives a clear triggering condition. There is no explicit when-not guidance or named alternative for agents that only need text/metadata rather than the PDF, which keeps it at 4.

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