Skip to main content
Glama
riemannzeta

USPTO Patent MCP Server

by riemannzeta
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

ppubs_get_citing_patents

Read-onlyIdempotent

Find later granted patents that cite a given patent (forward citations) to gauge influence, track follow-on work, or find later art.

Instructions

Find later granted patents that cite a patent (forward citations).

USE THIS TOOL WHEN: You want to know who built on a patent, gauge its
influence, or find later art in the same space. This is the working
replacement for the decommissioned Enriched Citation API. For the
references a patent itself cites (backward citations), read its front
page instead: ppubs_get_patent_by_number(number, sections=["biblio"])
returns them in usRefGroup, foreignRefGroup and otherRefPub.

Searches the references-cited field (.urpn.) of granted patents.
Published applications do not index that field, so citing
applications that have not yet issued are not included. Verified live
2026-09-26.

Args:
    patent_number: The cited patent ("7123456", "US 10,000,000 B2",
           "D845123" and "RE49123" all work)
    offset: Starting position for pagination (default: 0)
    limit: Maximum results to return (default: 20, max: 500)
    sort: Sort order (default: "date_publ desc", newest citing patent first)

Returns:
    Normalized search response; `total` is the forward-citation count
    and each result is a citing patent with GUID, title, dates,
    inventors and classification.

Input Schema

NameRequiredDescriptionDefault
sortNodate_publ desc
limitNo
offsetNo
patent_numberYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.8.1

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds substantive context beyond them: the search targets the .urpn. references-cited field, pending applications are not indexed so unissued citing applications are excluded, and it notes a live verification date. That coverage limitation is exactly the kind of behavior an agent cannot infer from structured fields.

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?

Well front-loaded: purpose, when-to-use, mechanism/caveats, then Args and Returns sections. The 'working replacement for the decommissioned Enriched Citation API' line and the verification date are marginal but defensible context; otherwise every sentence earns its place.

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 documents return shape (normalized search response, `total` as forward-citation count, per-result GUID/title/dates/inventors/classification). Combined with full parameter coverage and the index caveat, nothing needed to call it correctly is missing.

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 carries the full burden and does: patent_number accepts multiple formats ("7123456", "US 10,000,000 B2", "D845123", "RE49123"), offset is for pagination, limit defaults to 20 with a max of 500, and sort defaults to "date_publ desc" meaning newest citing patent first.

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+resource with scope: 'Find later granted patents that cite a patent (forward citations).' It explicitly distinguishes the direction of citation from the sibling ppubs_get_patent_by_number, which returns backward citations, so an agent can route correctly without opening either 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?

A dedicated 'USE THIS TOOL WHEN' block gives concrete intent triggers (who built on a patent, gauge influence, find later art) and names the alternative tool and its arguments for the opposite need (backward citations via ppubs_get_patent_by_number with sections=["biblio"]).

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