Skip to main content
Glama
Sign In
Errorbook MCP

Errorbook MCP

by stardustlil
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

调整错题优先级

adjust_priority

Adjust an error's priority by a specified delta on user request, with the adjustment decaying over 14 days and not affecting review scheduling.

Instructions

仅在用户明确要求提高或降低某编号优先级时调用。delta 为 -5..-1 或 1..5；影响按 14 天半衰期衰减，不会篡改 FSRS 或伪造复习。若用户说又做错了，应调用 record_review。

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>",
      "delta": "<delta>",
      "reason": "<reason>",
      "idempotency_key": "<idempotency_key>"
    },
    "name": "adjust_priority"
  }
}

Input Schema

NameRequiredDescriptionDefault
deltaYes
numberYes
reasonYes
idempotency_keyYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations, the description carries full transparency burden and delivers useful context: delta range, 14-day half-life decay, and assurance that FSRS is not tampered with or reviews faked. It does not cover edge cases like invalid numbers, but the provided behavior is substantive.

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, front-loaded with the trigger condition, and every sentence serves a purpose: usage, parameter meaning, or alternative. No wasted words.

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?

Given the low complexity and presence of an output schema, the description covers the core behavior and usage context well. Missing details on idempotency_key usage and edge cases are minor but would strengthen completeness.

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%, so the description must compensate. It explains delta's range and meaning, but the other three parameters (number, reason, idempotency_key) are left undefined beyond their names. This leaves a clear gap in parameter understanding.

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 adjusts priority of a numbered problem, with the trigger condition '仅在用户明确要求提高或降低某编号优先级时调用'. It explicitly distinguishes itself from sibling record_review, 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 Guidelines5/5

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

Provides explicit when-to-use guidance ('only when user explicitly requests priority change') and names the alternative tool record_review for the case where the user reports a mistake. This is clear usage differentiation.

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

Deploy Server

Other Tools