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

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

by proteus-vue

red_team

Critiques novel drafts to expose logic gaps, broken character motivation, forced coincidences, and reader drop-off risks 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": "red_team"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYes
revision_noteNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

B3/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 disclosure burden and falls short. It never says whether the tool is read-only or mutates the manuscript, what the response looks like (list of issues? scores? prose?), or how severe/actionable findings are framed. The deeper meaning of the revision_note input is left entirely unexplained.

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 clause, front-loaded with the tool's identity and then the specific flaw categories it targets. No filler, no repetition of the tool name as if it were a description.

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 two-parameter critique tool with no annotations and no output schema, the definition should explain the inputs and at least gesture at what a 'red team' result contains. As written, an agent knows the flavor of the critique but not how to feed or interpret it, leaving significant gaps relative to the tool's complexity and crowded sibling set.

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% and the description mentions neither parameter. That 'text' is the manuscript under review can be guessed, but 'revision_note' is genuinely ambiguous — a change log, a note to the reviewer, or context about the latest revision — and nothing in the description or schema disambiguates it.

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?

States a specific operation — adversarial critique that hunts for logic holes, broken motivation, contrived coincidence, and reader-abandonment points. The four named flaw categories make the tool's role concrete. It does not explicitly contrast itself with overlapping siblings such as blind_review, review_chapter, or check_self_consistency, so the agent must still infer the boundary.

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?

Usage is only implied: the word '挑刺' (nitpick) signals a post-draft adversarial pass, but the description never says when this should be chosen over blind_review, review_chapter, or check_consistency. No prerequisites, no exclusions, and no statement about whether it should run before or after other checks.

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