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

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

by proteus-vue

review_batch

Review novel chapters in batches to detect cross-chapter drift, measure revision impact, and flag chapters needing re-review before submission.

Instructions

批次评审:影响半径增量 + 摘要金字塔跨章反漂移 + 复审铁律触发。chapters=[{id,text}]。

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": "review_batch"
  }
}

Input Schema

NameRequiredDescriptionDefault
factsNo
personaNo
chaptersYes
platformNoqimao
revised_idsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

C2.4/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 behavioral burden. It mentions impact-radius increments, cross-chapter anti-drift checks, and review-rule triggering, but these are unexplained slogans; it does not state side effects, permissions, whether the operation is read-only, or what the review returns.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is short and includes the required parameter shape, but it is front-loaded with dense jargon that is not self-explanatory. It is concise without being informative.

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

Completeness2/5

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

For a five-parameter batch review tool with no annotations, no output schema, and 0% schema description coverage, this description is far too thin. It does not explain what the batch review checks, how the optional parameters alter behavior, or what the agent should expect back.

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% and there are five parameters. The description only clarifies that chapters is a list of {id,text} objects; it says nothing about facts, persona, platform, or revised_ids, leaving most parameters undocumented in both schema and description.

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

Purpose3/5

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

The phrase '批次评审' identifies a batch review operation, which distinguishes it at a high level from single-chapter siblings like review_chapter. However, the rest of the description ('影响半径增量 + 摘要金字塔跨章反漂移 + 复审铁律触发') is opaque internal jargon and does not clearly explain what the tool actually reviews or produces.

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 explicit when-to-use or when-not-to-use guidance, and no named alternative such as review_chapter or blind_review. The only implied guidance is that this is the batch variant, which an agent must infer from the name.

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