tw-patent-mcp

ops_biblio

Read-onlyIdempotent

Retrieves EPO OPS bibliographic data—title, applicants, inventors, priority, IPC/CPC, citations, abstract, and family ID—from a publication number, with optional raw JSON output.

Instructions

EPO OPS 書目資料（標題、申請人、發明人、優先權、IPC/CPC、引證、摘要、家族 id）。number 照公報號寫即可，例：EP1000000、TW201644272A、TWI700000B、TWM600000U、US10000000B2；程式自動轉成 docdb 格式。預設回壓平摘要，raw=true 回原始 JSON。

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "number": "<number>"
    },
    "name": "ops_biblio"
  }
}

Input Schema

Name	Required	Default
`fmt`	No	auto
`raw`	No
`number`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.2.0Oct 23, 2026

addedInput schema / properties / raw

Added value: +{
+  "default": false,
+  "title": "Raw",
+  "type": "boolean"
+}

First observedv0.1.0Oct 20, 2026

TDQS

A4.7/5.0

Behavior5/5

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

The description goes beyond simple retrieval by detailing operational behaviors: the program automatically converts the output to docdb format, and it explicitly defines the difference between the default return (flattened abstract) and the 'raw=true' mode (original JSON). This is critical execution context.

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 densely packed but highly efficient. It covers scope, input format, output format, and transformation process without unnecessary 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?

Given the 0% schema coverage, the description is maximally complete. It details the resources returned (all bibliographic fields), the input format required, and the specific operational output options (docdb vs. raw JSON).

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?

Since schema description coverage is 0%, the description is essential. It provides vital format guidance for the 'number' parameter (patent number conventions) and explains the effect of the 'raw' parameter, adding semantic depth beyond the input schema alone.

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 retrieves bibliographic data (metadata like Title, Applicant, IPC/CPC, Abstract) specifically from the EPO OPS domain. It immediately distinguishes itself by listing the specific data points returned, making its function unambiguous.

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?

It dictates the format for the required 'number' parameter using specific examples (e.g., EP1000000, US10000000B2), which serves as a strong usage guideline. While it doesn't compare itself to siblings, the scope of metadata retrieval is clearly defined.

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

Deploy Server