Skip to main content
Glama

novel_style_report

Generates a six-dimensional style profile for a whole book to assess voice consistency and chapter-level variation. Use it for book-wide style reports and optional AI style judgment.

Instructions

全书6维风格画像(单章用style_check,技法用sentence_analysis)。

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>"
    },
    "name": "novel_style_report"
  }
}

Input Schema

NameRequiredDescriptionDefault
bookYes书名
rootNo书库根
briefNo精简摘要
actionNoreport(默认)/get
aiJudgmentNoAI风格判断

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv8.0.0
    • changedInput schema / properties / action / description
      Previous value: -"report=生成测量报告(默认);get=读取已保存的 AI 风格判断"New value: +"report(默认)/get"
    • changedInput schema / properties / aiJudgment / description
      Previous value: -"AI 的风格气质判断结论:后插件将测量数据与判断存入 style-reports 供后续使用"New value: +"AI风格判断"
    • changedInput schema / properties / book / description
      Previous value: -"书名(novels 下的子目录名)"New value: +"书名"
    • changedInput schema / properties / brief / description
      Previous value: -"true=返回精简摘要(一句话结论),省略=完整报告。"New value: +"精简摘要"
    • changedInput schema / properties / root / description
      Previous value: -"章节库根目录(含 novels 子目录)。"New value: +"书库根"
  2. First observed

TDQS

B3.3/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 and does not meet it. It never states that this is a read-only analysis, whether generation is expensive or long-running, what the six dimensions are, or what differs between the report and get actions exposed by the schema.

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 short sentence with the core scope front-loaded and the disambiguation parenthetical immediately after; no filler. It is arguably over-compressed, but that cost is already captured in the transparency and completeness dimensions rather than being padding.

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?

This is a five-parameter analytical tool with no annotations and no output schema, so the description must explain what a '6-dimension profile' returns and how report vs get behave. It says nothing about the dimensions, the report shape, or whether a prior report must exist for get, which leaves real gaps for a non-trivial tool.

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 the schema already documents all five parameters (book, root, brief, action, aiJudgment). The description adds no parameter guidance at all — notably it never explains the report-vs-get action distinction or what supplying aiJudgment does — so the baseline of 3 applies.

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 output: a whole-book 6-dimension style profile, which is clearly distinct from a single-chapter check or sentence-level technique analysis. The verb is implied rather than stated (the phrase is nominal, '6维风格画像'), but an agent can still tell exactly what resource this produces and how it differs from the two named siblings.

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?

It explicitly routes the agent: use style_check for a single chapter and sentence_analysis for technique-level questions, leaving this tool for book-wide profiling. That is genuine when-to-use-vs-alternative guidance, though it gives no exclusions, prerequisites (e.g. must the book be imported/analyzed first), or cost expectations.

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