Errorbook MCP

记录错题

create_problem

Save a confirmed problem draft to the error notebook, assign a unique immutable ID, and initialize FSRS scheduling. Idempotency key ensures safe retries without duplicate entries.

Instructions

保存宿主视觉模型已转写并确认的单道题，分配不可变编号并初始化 FSRS。不要把未确认的 OCR 猜测写入题库。幂等键用于安全重试。

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": {
      "draft": "<draft>",
      "idempotency_key": "<idempotency_key>"
    },
    "name": "create_problem"
  }
}

Input Schema

Name	Required	Default
`draft`	Yes
`idempotency_key`	Yes
`duplicate_policy`	No	return_existing

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 5, 2026

TDQS

A4.1/5.0

Behavior4/5

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

With no annotations, the description carries full burden. It discloses immutable numbering, FSRS initialization, and safe retry via idempotency key, which are meaningful behavioral traits. It also cautions against unconfirmed writes. It does not cover duplicate_policy semantics or auth, but overall it adds valuable context beyond a bare create operation.

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?

Three sentences with no redundancy. It front-loads the core action and adds warnings and retry context efficiently. Every sentence earns its place.

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

Completeness4/5

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

The description covers key aspects: saving confirmed data, immutable ID, FSRS initialization, and safe retry. The output schema exists, so return values need no explanation. It omits duplicate_policy semantics, but the schema's enum and default provide some guidance. Overall, it is complete enough for a create tool with a well-defined schema.

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 coverage is 0%, so the description must compensate. It explains idempotency_key's role (safe retry) but provides no additional meaning for draft or duplicate_policy. The draft structure is self-evident from the schema, but the description adds little beyond that, leaving a significant gap for two of three parameters.

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 saves a confirmed, transcribed single question, assigns an immutable number, and initializes FSRS. This specific verb+resource combination distinguishes it from siblings like update_problem and search_problems.

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 explicitly warns not to write unconfirmed OCR guesses, providing a clear when-not-to-use condition. It also implies use for confirmed data and mentions idempotency for safe retries. However, it does not name alternative tools or discuss scenario-based selection.

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

Deploy Server