Skip to main content
Glama
獬豸(Xiezhi)小说投稿评审 MCP Server

獬豸(Xiezhi)小说投稿评审 MCP Server

by proteus-vue

check_consistency

Detects cross-chapter inconsistencies in novels by validating fact contracts and comparing chapter summaries for conflicts, helping catch continuity errors before submission.

Instructions

跨章一致性:事实契约硬校验 + 摘要层 LLM 冲突发现。

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": {
      "chapters": "<chapters>"
    },
    "name": "check_consistency"
  }
}

Input Schema

NameRequiredDescriptionDefault
factsNo
chaptersYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

C2.8/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full burden, and it discloses only that one component is deterministic ('hard validation') and another invokes an LLM. It omits cost/latency implications of the LLM pass, what happens when the optional facts payload is absent, and what output or failure modes the agent should expect.

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?

A single front-loaded sentence with no filler, and the two mechanisms are clearly separated by a plus sign. Brevity is appropriate here, though it edges toward under-specification rather than economy.

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 two-parameter analysis tool with no output schema and no annotations, the definition covers the what but not the return value, the treatment of the optional facts input, or how results should be interpreted. It is minimally sufficient to avoid misuse but leaves real gaps for a tool that performs LLM-based conflict detection.

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% for both parameters. The words '事实契约' and '摘要层' faintly gesture at facts and chapters respectively, but the description never states that facts is optional and defaults to null, nor what shape chapter objects must take, so it does not compensate for the coverage gap.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a concrete operation (cross-chapter consistency checking) and splits it into two named mechanisms: hard validation of a fact contract plus LLM-based conflict discovery over summaries. That is more specific than a restated name, but it never distinguishes itself from the sibling check_self_consistency, so an agent cannot tell the two apart from the text alone.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

There is no when-to-use guidance at all: nothing says to call this after drafting a new chapter, before publishing, or instead of check_self_consistency or check_redline. The only usage signal is implicit in the phrase 'cross-chapter', leaving the agent to infer timing and alternatives.

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