Skip to main content
Glama

novel_style_check

Detect style drift by comparing a chapter’s fingerprint with the whole-book baseline, then use the deviation results to guide revisions.

Instructions

风格自检:对比单章与全书指纹输出偏差(改稿用 fix_plan,全书画像用 style_report)。

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": {
      "book": "<book>",
      "chapter": "<chapter>"
    },
    "name": "novel_style_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
bookYes书名
rootNo书库根
chapterYes章节

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv8.0.0
    • changedInput schema / properties / book / description
      Previous value: -"书名。"New value: +"书名"
    • changedInput schema / properties / chapter / description
      Previous value: -"要检查的章节(章号/文件名/标题)。"New value: +"章节"
    • changedInput schema / properties / root / description
      Previous value: -"章节库根目录。"New value: +"书库根"
  2. First observed

TDQS

A4/5.0
Behavior3/5

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

With no annotations, the description must carry the behavioral burden. It does disclose the output ('输出偏差'), making clear this is a diagnostic comparison rather than a mutation, but it says nothing about whether it writes any files, how large the deviation output is, or how failures (e.g. missing chapter) are handled.

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

Conciseness5/5

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

One front-loaded sentence with the core action first and the sibling routing in a parenthetical. Every clause earns its place; no filler or restatement of the title.

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 three-parameter read-style diagnostic with a fully documented schema and no output schema, the definition covers purpose, output nature and alternatives. Only the mutation/side-effect question is left implicit, which is a minor gap given the '自检' framing.

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 description coverage is 100%, so book, root and chapter are already documented in the schema. The description adds no meaning about how chapter scoping interacts with the whole-book baseline (e.g. whether the chapter must belong to the given book), so the baseline 3 applies.

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

Purpose5/5

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

States a specific verb and resource: it compares a single chapter's fingerprint against the whole-book fingerprint and outputs deviations. It also names the two sibling tools it is not (fix_plan, style_report), so an agent can distinguish it without opening any schema.

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

Usage Guidelines4/5

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

Explicitly routes the agent to alternatives: use fix_plan for revision work and style_report for a whole-book portrait, which implies this tool is for per-chapter deviation checking. It stops short of an explicit when-not statement for this tool itself, but the alternative routing is clear and actionable.

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