pdf-rescue-mcp

Overview Schema Source Related Servers Discussions Admin

更新专业术语词表

update_term_glossary

Add a verified typo replacement to a book-specific glossary using confirmed page evidence. Rejects uncertain or cross-line corrections.

Instructions

依据已核对的页面证据，向书名限定词表加入一条明确错字替换；不支持不确定或跨行替换。

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": {
      "rule_name": "<rule_name>",
      "title_keywords": "<title_keywords>",
      "wrong": "<wrong>",
      "right": "<right>"
    },
    "name": "update_term_glossary"
  }
}

Input Schema

Name	Required	Description	Default
`right`	Yes
`wrong`	Yes
`rule_name`	Yes
`title_keywords`	Yes

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 2, 2026

TDQS

A3.9/5.0

Behavior3/5

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

With no annotations, the description carries the transparency burden. It discloses the key constraints (no uncertain/cross-line replacements) and its title-scoped behavior, but does not mention whether existing rules are overwritten, permission requirements, or other mutation side effects.

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, well-structured sentence that is front-loaded with the action and includes necessary scope and constraints without filler. It is highly concise while remaining informative.

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?

For a mutation tool with four required parameters and no annotations, the description is somewhat sparse: it does not provide usage alternatives or explain rule_name. The output schema covers return shape, but overall behavioral and parameter completeness remain partial.

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 0%, but the description adds meaning by indicating that wrong/right form a typo replacement pair and that title_keywords scope the rule via '书名限定词表'. However, rule_name is not semantically addressed, leaving a gap for one of the four required 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?

Description states a specific action: based on verified page evidence, add a clear typo replacement to a title-scoped glossary. It clearly distinguishes itself from sibling tools like get_term_glossary (read-only) and other extraction/diagnosis tools.

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?

The description provides clear usage context: only use with verified page evidence, and explicitly excludes uncertain or cross-line replacements. It does not name alternative tools, but the when/when-not conditions are clearly stated.

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