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

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

by proteus-vue

check_chapter_end

Evaluate a chapter’s ending to determine whether it contains a hook and assess its strength, helping authors verify chapter-end pull before submission.

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": {
      "text": "<text>"
    },
    "name": "check_chapter_end"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

C2.3/5.0
Behavior2/5

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

No annotations exist, so the description carries the full behavioral burden, yet it discloses almost nothing: no output shape, no scoring scale for "强度", no thresholds for what counts as a weak hook, and no indication of whether the input is truncated or chunked. The single word "强度" hints that a graded result is returned, but nothing more.

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

Conciseness2/5

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

Brevity here is under-specification rather than concision: one nine-character fragment with no structure, no lead sentence stating the task, and no follow-up detail. Almost nothing is wasted because almost nothing is present.

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?

With no annotations, no output schema, and an undocumented input parameter, the description should explain both the input contract and the shape of the returned judgment. It supplies neither, leaving the agent unable to predict what it will get back or how to prepare the text.

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% for the single required parameter "text", and the description adds no clarification. It does not say whether text should be the final paragraphs, an outline, or the whole chapter — a critical distinction for a chapter-ending hook check.

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

Purpose3/5

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

"章末钩子判定与强度" names a specific resource (chapter-end hook) and two operations (judging, strength scoring), which is more than a bare restatement of the tool name. However, it is a compressed noun phrase with no verb framing, so the agent must infer that it analyzes a supplied chapter ending rather than, say, retrieving stored hook data.

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?

There is no statement of when to use this versus siblings such as check_opening, check_pacing, or review_chapter, and no prerequisites or exclusions. The only implicit guidance comes from the word "章末" (chapter end), which narrows scope but says nothing about workflow position.

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