Skip to main content
Glama

novel_keywords

Count high-frequency two- and three-character Chinese words and English terms across a whole book or selected chapter, excluding single characters, to reveal vocabulary patterns.

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

Input Schema

NameRequiredDescriptionDefault
topNo数量(默认20)
bookYes书名
rootNo书库根
chapterNo章节(省=全书)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 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: +"书库根"
    • changedInput schema / properties / top / description
      Previous value: -"返回的关键词数量。默认 20。"New value: +"数量(默认20)"
  2. First observed

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description must carry behavioral weight; it does disclose the substantive trait that single-character tokens are excluded and only 2–3 character Chinese words plus English words count. It says nothing about what the output looks like, cost of scanning a whole book, or whether the operation is read-only, which for an unannotated tool leaves real gaps.

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?

A single compact sentence that front-loads the verb and scope, then qualifies the counting rule in parentheses. Nothing is redundant or padded.

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 four-parameter, single-required-parameter analysis tool with full schema coverage and no output schema, the description covers the essential semantics including the chapter-omitted-means-whole-book behavior. The only modest omission is that the result format is never hinted at, which matters slightly since no output schema exists.

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 top (default 20), book, root, and chapter. The description only reinforces the chapter-vs-whole-book semantics via 全书/单章 and adds nothing about top or root; baseline 3 is correct.

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 verb plus resource (统计…高频词) and pins the scope (全书/单章) and the counting rule (二三字词与英文,不含单字), so an agent knows this is a frequency analysis over 2–3 character words and English tokens. It is clear but does not distinguish itself explicitly from siblings such as novel_lexicon or novel_style_report, so no sibling differentiation credit.

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?

Scope usage is implied: a chapter value gives single-chapter statistics, omitting it gives whole-book statistics, which maps onto the schema's chapter parameter ('省=全书'). There is no explicit when-to-use vs. when-not guidance and no named alternative among the many sibling analysis tools.

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