Epo Ops

Get Biblio

get_biblio

Read-onlyIdempotent

Bibliographic data for one published patent — title, inventors, applicants, publication date, IPC classifications. Drawn from EPO DOCDB, which covers 100+ patent offices, so Chinese, Japanese, Korean and US publications resolve as well as European ones. Give the publication number as printed on the document; a trailing kind code such as the "A" in "CN117928705A" is handled for you.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`number`	Yes	Publication number as printed on the document, e.g. "EP1234567", "CN117928705A", "US10000000". Spaces, commas and slashes are ignored, and a trailing kind code (the "A" / "A1" / "B1" suffix) is retried without it if the exact form is not indexed.

Output Schema

TableJSON Schema

Name	Required	Description
`parties`	No	Inventors, applicants, and other parties
`invention-title`	No	Title of the invention
`priority-claims`	No	Priority claim information
`classifications-ipcr`	No	IPC classifications
`application-reference`	No	Application reference details
`publication-reference`	No	Publication reference including number, date, status

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedAug 6, 2026

changedInput schema / examples

Previous value: -[
-  {
-    "number": "EP1234567"
-  }
-]New value: +[
+  {
+    "number": "EP1234567"
+  },
+  {
+    "number": "CN117928705A"
+  }
+]

changedInput schema / properties / number / description

Previous value: -"Patent number in epodoc format, e.g. \"EP1234567\""New value: +"Publication number as printed on the document, e.g. \"EP1234567\", \"CN117928705A\", \"US10000000\". Spaces, commas and slashes are ignored, and a trailing kind code (the \"A\" / \"A1\" / \"B1\" suffix) is retried without it if the exact form is not indexed."

Changed2 schema fields changedMay 22, 2026

addedInput schema / examples

Added value: +[
+  {
+    "number": "EP1234567"
+  }
+]

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "description": "Bibliographic data for a patent",
+  "properties": {
+    "application-reference": {
+      "description": "Application reference details",
+      "type": "object"
+    },
+    "classifications-ipcr": {
+      "description": "IPC classifications",
+      "type": "object"
+    },
+    "invention-title": {
+      "description": "Title of the invention",
+      "type": "object"
+    },
+    "parties": {
+      "description": "Inventors, applicants, and other parties",
+      "type": "object"
+    },
+    "priority-claims": {
+      "description": "Priority claim information",
+      "type": "object"
+    },
+    "publication-reference": {
+      "description": "Publication reference including number, date, status",
+      "type": "object"
+    }
+  },
+  "type": "object"
+}

First observedMay 13, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior. The description adds valuable context beyond these: the data source (EPO DOCDB), broad office coverage (100+), and normalization of trailing kind codes. This explains input handling and data provenance, which annotations do not cover.

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 two sentences, front-loaded with the core purpose, then adding source and input handling details. Every sentence earns its place with no redundancy or filler.

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 tool is simple (one parameter), has an output schema, and strong safety annotations. The description covers the tool's output scope, data source, geographical coverage, and input format nuances, making it sufficiently complete for an agent to select and invoke it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema already thoroughly documents the 'number' parameter including examples, ignored characters, and kind code handling. The tool description reiterates the kind code handling but adds no new semantic meaning beyond the schema, so it meets the baseline of 3.

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 function: retrieving bibliographic data for one published patent, listing specific fields (title, inventors, applicants, publication date, IPC classifications). It is distinct from sibling tools like get_abstract or get_claims, as it focuses on bibliographic metadata rather than content.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies when to use this tool: when you need bibliographic data for a specific patent publication, not for searching or for full text. It provides input guidance (publication number as printed, kind codes handled) and notes global coverage. However, it does not explicitly name alternative tools or state when not to use it, so it falls short of a 5.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Epo Ops tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.