Skip to main content
Glama
riemannzeta

USPTO Patent MCP Server

by riemannzeta
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

ppubs_get_full_document

Read-onlyIdempotent

Retrieve a complete patent or application document by GUID, optionally limiting output to sections like biblio, abstract, claims, or description to reduce token use.

Instructions

Get complete patent document by GUID from PPUBS.

USE THIS TOOL WHEN: You have a document GUID from search results
and need the patent text. A whole document runs 20-40k tokens, most
of it the description — ask for `sections` when you need less.

Args:
    guid: Document GUID (e.g., "US-9876543-B2")
    source_type: Document type - "USPAT" for patents, "US-PGPUB" for applications
    sections: Which parts to return; omit for everything. Any of
           "biblio" (front-page data: parties, dates, classification,
           references cited), "abstract", "claims", "description".
           ["biblio", "claims"] answers most questions in ~5k tokens.

Returns:
    Document with the requested sections. Empty fields and search
    highlight fields are dropped.

Input Schema

NameRequiredDescriptionDefault
guidYes
sectionsNo
source_typeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.8.1
    • addedInput schema / properties / sections
      Added value: +{
+  "anyOf": [
+    {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Sections"
+}
    • changedOutput schema / (root)
      Previous value: -{
-  "properties": {
-    "result": {
-      "additionalProperties": true,
-      "title": "Result",
-      "type": "object"
-    }
-  },
-  "required": [
-    "result"
-  ],
-  "title": "ppubs_get_full_documentOutput",
-  "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 cover read-only/idempotent/open-world, so the description correctly spends its budget on behavior they cannot express: typical document size (20-40k tokens, mostly description), the fact that omitting `sections` returns everything, per-section token economics, and that empty/highlight fields are dropped. This is materially useful operational context.

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 purpose and usage guidance, with Args/Returns blocks that are easy to scan. The per-argument prose is slightly long for a three-parameter tool, but every sentence carries actionable content, so waste is minimal.

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, the description still states the return shape ('document with the requested sections') and the field-dropping behavior, and it warns about token cost before the call. Nothing essential is missing for correct invocation.

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 must carry the load and it does: it gives a GUID example, enumerates source_type values ('USPAT', 'US-PGPUB'), and defines every section token ('biblio', 'abstract', 'claims', 'description') plus the default (omit = everything) and a recommended combination.

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 ('Get complete patent document by GUID from PPUBS') and clarifies the retrieval channel ('GUID from search results'), which separates it from siblings like ppubs_get_patent_by_number and ppubs_download_patent_pdf. An agent can identify the tool without opening the 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' block names the precondition (you already have a GUID from search results) and offers a scoped alternative (request `sections` when you need less). The routing condition is unambiguous.

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