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

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

by proteus-vue

check_redline

Checks novel text against platform redline rules and keyword scores before submission, flagging fatal violations that prohibit publication.

Instructions

L1 形态红线 + L2 关键词打分,毫秒级;致命项直接判禁止发布。

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

Input Schema

NameRequiredDescriptionDefault
textYes
platformNoqimao
chapter_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

C2.2/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 burden. It does disclose useful behavior beyond structure: millisecond-level latency and that fatal hits produce a hard 'do not publish' verdict. But it says nothing about the decision output format (no output schema exists), what non-fatal L2 scores look like, or whether the check is purely local/read-only.

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?

It is a single compact sentence with the mechanics and the outcome front-loaded, so there is no padding. But the brevity comes at the cost of clarity: unexplained 'L1/L2' labels and a semicolon-joined clause leave the reader guessing at the structure of the check.

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?

For a three-parameter tool with no annotations and no output schema, the description should explain the verdict/score return shape and the platform parameter's role. Neither is present, so an agent can supply `text` but cannot confidently set `platform`/`chapter_id` or interpret what comes back.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% for three parameters, so the description must supply the meaning. It never mentions `text`, `platform` (which defaults to 'qimao' and clearly selects a platform rule set), or `chapter_id`, leaving two of three parameters entirely undefined anywhere in the definition.

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 names a two-stage check (L1 '形态红线' form redline plus L2 keyword scoring) and states the outcome rule (fatal items are judged blocked from publishing), which is more specific than a name restatement. However, the terminology is unexplained jargon and nothing distinguishes it from siblings such as platform_fit or red_team, which perform plausibly overlapping review functions.

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 reach for this tool versus the many other check_* / review tools, and no prerequisites or exclusions are given. The implied use case (fast pre-publish redline screening) is only inferable from the words '毫秒级' and '禁止发布', not stated as guidance.

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