Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

googlepatents_detail

Retrieve a patent's bibliographic data, abstract, claims, description, citations, cited-by patents, and family by publication number.

Instructions

A single patent's bibliographic data, abstract, claims, description, citations, and family. Returns a single patent's detail: title, abstract, inventors, assignees, dates, legal status, CPC/IPC classifications, claims, description, patent citations, cited-by patents, family members, and similar documents. number is a publication number such as US10758101B2, EP1000000A1, or WO2020123456A1. To search or browse by keyword, inventor, or assignee instead of a known publication number, use /googlepatents/search.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
langNoLanguage code for the translated page, default en
numberYesPublication number, e.g. US10758101B2

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.14.0

TDQS

A4.2/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It does disclose the shape and breadth of what comes back (including cited-by and family, which go beyond a naive fetch), which is useful given there is no output schema. However it says nothing about rate limits, auth requirements, whether the number must match exactly, or failure behavior for an invalid/withdrawn publication number.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loads the resource and routing guidance, but the first two sentences overlap heavily — both enumerate the returned fields (abstract, claims, description, citations, family appear twice). One of those enumerations could be dropped with no loss.

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 only one required parameter and no output schema, the field inventory substitutes usefully for a return-value description, and the sibling routing is covered. Minor gaps remain around error handling and pagination/limits for the citation and family lists.

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 coverage is 100%, so the baseline is 3, and the description adds value by giving three concrete publication-number formats across jurisdictions (US10758101B2, EP1000000A1, WO2020123456A1) versus the schema's single US example. It also reinforces that `number` is a publication number, not an application or patent ID. It adds nothing for the `lang` 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?

States a specific resource (a single patent's detail) and enumerates the exact payload: title, abstract, inventors, assignees, dates, legal status, CPC/IPC, claims, description, citations, cited-by, family, similar documents. The final sentence explicitly distinguishes it from /googlepatents/search, so an agent can separate it from googlepatents_suggest/classification/coverage/recent without opening schemas.

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?

Gives the selecting condition (you must already have a known publication number) and names the alternative to use otherwise (search or browse by keyword, inventor, or assignee via /googlepatents/search). Both when-to-use and when-not-to-use are stated.

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