Epo Ops

Get Abstract

get_abstract

Read-onlyIdempotent

Fetch the abstract text of a published patent from EPO OPS. Give the publication number as printed on the document; a trailing kind code is handled for you. Requires _apiKey=consumer_key:consumer_secret.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`number`	Yes	Publication number as printed on the document, e.g. "EP1234567", "CN117928705A", "US10000000", or a PCT international publication like "WO2025028566" / "WO 2025/028566" / "WO2025028566A1". 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	Default
`abstract`	No	Abstract content

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 20, 2026

changedInput schema / properties / number / description

Previous 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."New value: +"Publication number as printed on the document, e.g. \"EP1234567\", \"CN117928705A\", \"US10000000\", or a PCT international publication like \"WO2025028566\" / \"WO 2025/028566\" / \"WO2025028566A1\". 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."

Changed1 schema field changedAug 6, 2026

changedInput schema / properties / number / description

Previous value: -"Patent number, epodoc format"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 24, 2026

addedInput schema / examples

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

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "description": "Abstract text and metadata for a patent",
+  "properties": {
+    "abstract": {
+      "description": "Abstract content",
+      "properties": {
+        "p": {
+          "oneOf": [
+            {
+              "type": "string"
+            },
+            {
+              "description": "Abstract paragraphs",
+              "items": {
+                "type": "string"
+              },
+              "type": "array"
+            }
+          ]
+        }
+      },
+      "type": "object"
+    }
+  },
+  "type": "object"
+}

First observedMay 13, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive, and open-world behavior. The description adds useful context beyond annotations by naming the data source (EPO OPS) and specifying the authentication requirement (_apiKey=consumer_key:consumer_secret).

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 three short sentences, front-loaded with the core purpose, followed by practical input guidance and authentication requirements. Every sentence contributes useful information without redundancy.

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 one fully described parameter, rich annotations, an output schema, and the description covering source, auth, and numbering behavior, the definition gives an agent everything needed to invoke the tool 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%, and the schema already documents the publication number format in detail, including examples and normalization behavior. The description reinforces that a trailing kind code is handled but does not add meaning beyond the schema, so the baseline of 3 applies.

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 states a specific verb and resource: fetch the abstract text of a published patent from EPO OPS. This clearly distinguishes it from siblings like get_claims or get_biblio, which retrieve different patent data.

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

Usage Guidelines3/5

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

The description implies when to use the tool by naming the resource it returns, but it does not explicitly compare it to siblings such as get_biblio or get_claims. It also provides input guidance for the publication number but no when-not-to-use conditions.

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

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.