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

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

by proteus-vue

review_chapter

Runs a multi-stage pre-submission review of a novel chapter, checking compliance, content quality, tone drift, and platform fit so you can identify issues before submission.

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

Input Schema

NameRequiredDescriptionDefault
textYes
factsNo
personaNo
platformNoqimao
chapter_idNo
revision_noteNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

C2.9/5.0
Behavior3/5

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

With no annotations, the description bears the full disclosure burden, and it does add one real behavioral trait: '硬拒短路' tells the agent the pipeline terminates early on a compliance failure. It says nothing about cost/latency of the multi-stage run, whether any state is written, or how results are reported. That leaves meaningful gaps for an unannotated tool.

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 arrow-delimited sentence that front-loads the pipeline and wastes no words. It is dense with domain jargon, but the structure is efficient for its length.

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 six-parameter, multi-stage review tool with no annotations and no output schema, the description only labels the stages. It omits what each stage produces, how the agent should interpret a hard rejection versus a drift flag, and what any of the parameters change, which is insufficient given the tool's complexity.

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% across six parameters (text, facts, persona, platform, chapter_id, revision_note), and the description mentions none of them. Concepts like 'platform' defaulting to 'qimao' or how 'facts' and 'revision_note' alter the review are completely undocumented, so the description 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 specific operation (single-chapter review) and enumerates the pipeline stages: compliance positioning with a hard-reject short-circuit, content quality, final drift review, red-team critique, and benchmark comparison. This is clearly more than a restatement of the name. It stops short of differentiating itself from siblings like red_team, benchmark, or blind_review, which appear to be sub-components of this pipeline.

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 alternative is named. The agent must infer that this is the full single-chapter review workflow rather than a batch (review_batch) or blind (blind_review) path, purely from the phrase '单章' (single chapter).

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