docdb-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DOCDB_API_URL | Yes | The URL of the DOCDB API server |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| resolve_docdb_idA | 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:
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):
|
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
Only one tool exists, so there is no possibility of confusion or ambiguity between tools.
The single tool name follows a clear verb_noun pattern (resolve_docdb_id) and is self-explanatory.
A single tool is minimal but can be appropriate for a very focused purpose like patent ID resolution. However, it feels thin for any broader use case.
The server covers only ID resolution, missing related operations like search, listing, or batch processing. For a narrow purpose it may be sufficient, but agents have no fallback if resolution fails.