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

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

by proteus-vue

check_pacing

Analyze chapter pacing by measuring hook, conflict, and payoff density and flagging pacing deserts, helping authors find slow sections 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_pacing"
  }
}

Input Schema

NameRequiredDescriptionDefault
chaptersYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

B3/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, and it does disclose one real behavioral trait: computation is mostly deterministic with LLM involvement limited to cross-chapter probing. However it says nothing about cost, whether it is read-only, or what a '节奏荒漠' result looks like, and there is no output schema to fall back on.

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 short clauses, metric scope front-loaded ahead of the implementation note, with no filler. It is terse to the point of being cryptic in places, but every clause carries information.

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 tool with one opaque parameter, no annotations, and no output schema, the description identifies what is analyzed and roughly how, which is the minimum an agent needs to choose it. It still leaves unresolved how to structure the input and what the result contains.

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?

The single required parameter 'chapters' has 0% schema description coverage and is an open object with additionalProperties, yet the description says nothing about what fields each chapter entry must contain (text, index, word count?). The caller must guess the shape, and the description does nothing to compensate.

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?

Names a specific verb and resource (节奏检查 = pacing check) and enumerates exactly what it measures: 爽点/冲突/钩子密度 plus 节奏荒漠检测. That is concrete and distinguishes it from generic siblings like check_consistency, though no sibling is named explicitly for contrast.

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?

The description explains how the check runs (machine layer primary, LLM only as cross-chapter probe) but never says when to call it, in what workflow stage, or why to prefer it over check_chapter_end or check_opening. The agent must infer the use case from the tool name alone.

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