Skip to main content
Glama

resolve_docdb_id

Convert a patent publication number into a standardized DOCDB record, returning inventor name, publication date, and family ID. Requires country code and number without kind code.

Instructions

Resolve a patent publication number to its canonical DOCDB record(s).

IMPORTANT — strip the kind code before calling: "US8000000B2" → cc="US", number="8000000" "EP1234567A1" → cc="EP", number="1234567" "WO2013143024" → cc="WO", number="2013143024" The kind code (trailing letter+digit suffix like B2, A1, A2, U1) is NEVER part of the number argument. Passing it causes an empty result, not an error.

Also strip formatting: "US 8,000,000" → cc="US", number="8000000".

Leading zeros in the number are ignored: "08000000" and "8000000" are equivalent.

Args: cc: Two-letter DOCDB country code, e.g. "US", "EP", "WO", "DE", "JP", "FR", "GB", "CN", "KR". Must be exactly 2 characters. number: Publication number without kind code or country prefix, digits and letters only (no hyphens, spaces, or slashes).

Returns: List of matching records, each with: - docdb_id: full DOCDB ID including kind code, e.g. "US8000000B2" - inventor: first inventor full name in caps, e.g. "ROBERT J. GREENBERG" - date_publ: publication date as YYYYMMDD, e.g. "20110816" - family_id: DOCDB patent family ID, e.g. "39183031" Multiple records mean the same publication number has several document variants (e.g. an A1 and a B2 publication of the same application). Empty list means no match — not an error.

If you get an empty list:

  1. Check that you stripped the kind code (most common mistake).

  2. Consider common transcription errors in the source material: O/0, I/1, S/5, B/8. Try plausible substitutions in the number.

  3. Use all context available to you (inventor name, year) to reconstruct the most likely number and retry.

Processing the output: The tool returns the first inventor and publication date. These map directly onto the way patents are cited in practice: "Greenberg", "Greenberg et al.", or "Greenberg et al. (2011)" in a source document should match inventor "ROBERT J. GREENBERG" and date_publ starting with "2011". Use that correspondence to verify the match. If you get multiple records, compare inventor names and publication dates across the candidates to select the most likely one. In all cases you must decide: the tool gives you candidates, not a verdict.

Error codes returned by the server (not exceptions):

  • "cc_does_not_exist": cc is not a recognized DOCDB country code — check spelling or try the ISO 2-letter code for the country.

  • "number_is_not_alnum": number contains illegal characters such as hyphens, slashes, or spaces — strip them before retrying.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ccYes
numberYes

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 fully discloses behavior: it explains the output structure, the meaning of multiple records, error codes returned (not exceptions), and edge cases like leading zeros. It does not contradict any annotations (none provided).

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?

The description is well-structured with sections (IMPORTANT, Args, Returns, troubleshooting) and front-loaded with critical instructions. It is somewhat lengthy but every sentence serves a purpose. Minor redundancy (e.g., list of country codes) could be trimmed but overall efficient.

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?

The description covers input preparation, output interpretation, error handling, and edge cases. It includes troubleshooting guidance and processing advice. There are no sibling tools, so no differentiation needed. It is complete for the given complexity and schema richness.

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%, but the description thoroughly explains both parameters: cc (two-letter DOCDB country code with examples) and number (publication number without kind code, formatting, or special characters). It includes constraints and typical values.

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's purpose: 'Resolve a patent publication number to its canonical DOCDB record(s).' It specifies the exact action (resolve) and the resource (patent publication number to DOCDB records). No ambiguity.

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?

The description provides explicit instructions on how to prepare inputs (strip kind code, format numbers), gives examples, troubleshooting steps for empty results, and advice on using context. Although no siblings are listed, the guidance is comprehensive and directly applicable.

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/gui11aume/docdb-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server