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

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

by proteus-vue

check_self_consistency

Detects within-chapter inconsistencies such as timeline regressions, conflicting numbers, and inconsistent character titles, returning suspect flags with source evidence and no fatal verdict.

Instructions

单章内部自洽弱信号:时序倒退/数字互斥/称谓变体。零成本,只报 suspect 与原文证据,不判 fatal。

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": {
      "text": "<text>"
    },
    "name": "check_self_consistency"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full burden; it does disclose the output character (only 'suspect' plus原文 evidence) and its non-blocking stance ('不判 fatal'), which is real behavioral context. It omits whether the operation is read-only/pure, how large a text it accepts, and any failure behavior.

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?

Two dense clauses, front-loaded with the signal taxonomy followed by the cost/behavior constraint; no filler. It is terse to the point of terseness — terms like '称谓变体' assume domain vocabulary — but nothing is redundant.

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?

For a single-input, no-output-schema analysis tool, the description covers scope (three signal types), output shape (suspect + quoted evidence), and its non-authoritative status. Only the input contract and the exact result structure remain unstated.

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 coverage is 0% and the single parameter 'text' is undocumented in both schema and description. The description's '单章内部' framing implies the parameter is one chapter's text, but the expected size, format, or that it must be a single chapter is never made explicit.

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 specific check ('单章内部自洽弱信号') and enumerates the three signal classes it detects: temporal regression, numeric mutual exclusion, and appellation variants. The '单章内部' scope marker implicitly contrasts with the broader sibling check_consistency, but that sibling is never named, so differentiation is left to inference.

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

Usage Guidelines3/5

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

'零成本' signals this is a cheap pre-screen and '不判 fatal' signals it is non-decisive, which hints at when it fits in a review pipeline. However, it never states when to prefer it over check_consistency or check_redline, nor any prerequisites (e.g., that text must be a single chapter).

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