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

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

by proteus-vue

next_chapter_brief

Converts prior review findings, unresolved foreshadowing, and persona anchors into next-chapter writing constraints, producing a ready-to-use prompt for a drafting agent.

Instructions

评审回流:把上轮评审结论+未收伏笔+人设锚转成下一章写作约束块(含可直接喂给写稿 Agent 的 prompt)。

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": {
      "review": "<review>"
    },
    "name": "next_chapter_brief"
  }
}

Input Schema

NameRequiredDescriptionDefault
factsNo
reviewYes
personaNo
platformNoqimao
chapter_idNo
current_chapter_indexNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

B3.2/5.0
Behavior3/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 does disclose the output form (a constraint block containing a drafting prompt), which is useful given there is no output schema. It does not say whether the tool is pure computation or persists anything, whether the review object is mutated, or what happens when persona/facts are omitted. That side-effect ambiguity is the main unresolved behavioral question for a 6-parameter nested-object 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 sentence that front-loads the operation and then specifies the artifact produced, with the parenthetical clarifying that the output is directly consumable by a drafting agent. No filler, though the opening label '评审回流' costs a little decoding before the substantive clause arrives.

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?

With no annotations, no output schema, and nested object parameters, the description does well to characterize the return value, which is the biggest gap it could have left. However, it leaves four of six parameters unexplained and never states side effects or defaults, so an agent can invoke it but cannot confidently construct the facts/platform/chapter fields from the description alone.

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%, so the description must explain six parameters and it covers roughly three concepts: review conclusions, foreshadowing, and persona anchors. The remaining parameters — facts, platform (defaulting to 'qimao'), chapter_id, current_chapter_index — get no mention at all, and 'unresolved foreshadowing' does not map cleanly to any named parameter, leaving the agent to guess whether it arrives via facts or is derived from review.

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 transformation: it takes the previous review conclusions, unresolved foreshadowing, and persona anchors and turns them into a next-chapter writing-constraint block plus a ready-to-use drafting prompt. That distinguishes it from review-side siblings such as review_chapter or red_team, which produce verdicts rather than drafting constraints. The jargon '评审回流' is opaque at first read, but the rest of the sentence resolves it.

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?

Sequencing is implied by '上轮评审结论' — this runs after a review and before drafting the next chapter — but the description never states that explicitly, nor does it name any alternative tool or a condition under which not to use it. Adequate for an agent that already knows the review-to-draft pipeline; thin for one that does not.

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