Errorbook MCP

修正错题

update_problem

Correct or modify a problem's text, tags, choices, and metadata. Uses expected_version for conflict detection; on version mismatch, re-read the latest problem and apply changes again.

Instructions

修正 OCR 文本、标签等内容。必须传入读取时获得的 expected_version，冲突时重新读取，编号不会改变。

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>",
      "patch": "<patch>",
      "expected_version": "<expected_version>",
      "reason": "<reason>",
      "idempotency_key": "<idempotency_key>"
    },
    "name": "update_problem"
  }
}

Input Schema

Name	Required	Description	Default
`patch`	Yes
`number`	Yes
`reason`	Yes
`idempotency_key`	Yes
`expected_version`	Yes

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 5, 2026

TDQS

A4/5.0

Behavior4/5

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

With no annotations provided, the description carries the burden of disclosing behavior. It reveals the optimistic concurrency requirement (expected_version), the conflict resolution approach (re-read), and an important invariant ('编号不会改变' - number will not change). This is valuable beyond the schema, though it does not mention potential side effects or idempotency semantics.

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 a single, front-loaded sentence that conveys the core purpose, the critical prerequisite, and a key invariant. Every clause earns its place with no redundancy or fluff.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description covers the essential action and concurrency mechanism, and an output schema exists to document return values. However, it omits guidance on constructing the patch object, the purpose of reason/idempotency_key, and partial-update semantics, making it less complete for a tool with 5 required parameters and no annotations.

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

Parameters2/5

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

Schema description coverage is 0%, yet the description only explains one parameter (expected_version) and touches on '编号' (number) without detailing its role. The required parameters reason and idempotency_key are not explained at all, leaving the agent without sufficient understanding of why they are necessary or how to fill them.

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?

Description starts with '修正 OCR 文本、标签等内容' (correct OCR text, tags, etc.), clearly stating the action and target resource. This distinguishes it from sibling create_problem (creation) and get_problem (reading), making the purpose 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?

Provides a clear prerequisite: '必须传入读取时获得的 expected_version' (must pass expected_version obtained when reading), establishing when to use the tool relative to get_problem. It also advises on conflict handling ('冲突时重新读取'), but does not explicitly mention alternatives or when not to use it, so it falls short of full guidance.

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

Deploy Server