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

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

by proteus-vue

check_opening

Checks whether a novel opening meets submission criteria: the first 300 characters establish protagonist, conflict, and suspense, while the next 800 introduce the core advantage. Supports platform-specific review.

Instructions

黄金开篇:前 300 字主角/冲突/悬念 + 800 字金手指。

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_opening"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYes
platformNoqimao

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

C2.4/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. It hints at measurable thresholds (first 300 characters, 800 characters) but says nothing about whether the result is a pass/fail, a score, a rewrite suggestion, or whether calling it is read-only and stateless.

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

Conciseness3/5

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

A single short line with no filler, so it is front-loaded by default. However the phrasing is compressed to the point of being cryptic, mixing counts, slash-separated criteria, and jargon ('金手指') without any framing sentence.

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 two undocumented parameters, no annotations, and no output schema, the definition leaves the agent without enough to call it confidently or interpret results. It needs at least what input is expected and what the check returns.

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%, so neither 'text' nor 'platform' is documented anywhere. The description's character counts weakly imply that 'text' is the passage under review, but the 'platform' parameter (default 'qimao') and its effect on the criteria are entirely unexplained.

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?

The description reads as a criteria spec ('前 300 字主角/冲突/悬念 + 800 字金手指') rather than a statement of the action, so the verb must be inferred from the name 'check_opening'. It does convey the resource and the concrete dimensions being examined, which separates it from check_chapter_end, but no explicit statement of what the tool produces.

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 when-to-use guidance, no prerequisites, and no mention of any sibling such as check_pacing or check_redline for adjacent checks. The agent must guess whether this applies to an outline, a draft opening, or a full chapter.

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