Skip to main content
Glama
riemannzeta

USPTO Patent MCP Server

by riemannzeta

ppubs_search_patents

Search full text of granted US patents via USPTO Patent Public Search, returning current patent data updated daily.

Instructions

Search granted US patents in Patent Public Search (ppubs.uspto.gov).

USE THIS TOOL WHEN: You need full-text search of US patents with daily
updates, or need access to the most recent patent filings.

PREFER OVER patentsview_search WHEN: You need the most current data
(PPUBS updates daily vs PatentsView periodic updates).

Args:
    query: Search query using USPTO BRS syntax. Multi-word terms are
           AND-ed across all fields by default — quote phrases that
           must appear together. Examples:
           - '"machine learning"' - exact phrase, all fields
           - machine learning - both terms anywhere (AND)
           - '"neural network".ti.' - title contains phrase
           - smith.in. AND IBM.as. - inventor Smith, assignee IBM
           - G06N3/08.cpc. - CPC classification
           Field qualifiers are dotted suffixes (.ti., .ab., .in.,
           .as., .cpc., .pn.) — the legacy slash-prefix forms
           (TTL/, IN/, AN/, CPC/) no longer work: they silently
           return 0 results, and TTL/"phrase" returns a server 500.
           Default `sort="date_publ desc"` means broad queries return
           the latest grants first — narrow with field qualifiers
           to get relevant matches.
    offset: Starting position for pagination (default: 0)
    limit: Maximum results to return (default: 100, max: 500)
    sort: Sort order (default: "date_publ desc")

Returns:
    Normalized response with patent results including GUID, title,
    abstract, dates, inventors, and classification codes.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sortNodate_publ desc
limitNo
queryYes
offsetNo

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 carries full weight and does so thoroughly: it discloses legacy query syntax failures, silent zero-result behavior, and server 500 errors, plus default sort behavior that affects result relevance.

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 long but every section earns its place: usage guidance, parameter details, syntax pitfalls, and return summary are clearly structured and front-loaded with the most important decision information.

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 complex query language and the lack of annotations, the description covers usage context, query syntax, failure modes, default behavior, and return fields. The output schema reduces the need to document return values further.

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%, but the description fully compensates. The query parameter is documented with BRS syntax, field qualifiers, and multiple examples, while offset, limit, and sort all receive defaults and behavioral context.

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 tool searches granted US patents in Patent Public Search, with a specific verb and resource. It is also distinct from siblings like ppubs_search_applications and patentsview_search_patents.

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?

Provides explicit 'USE THIS TOOL WHEN' guidance and contrasts with patentsview_search based on data freshness. This tells the agent when to select this tool over a key alternative.

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