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

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

by proteus-vue

blind_review_package

Build a blind review input package that includes only manuscript text and prompts while excluding existing review fields, so independent reviewers can produce unbiased judgements.

Instructions

P2c 盲评输入包:只含正文+提示词,显式剔除既有评审字段,供独立评审员产出 judgements。

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": {
      "chapters": "<chapters>"
    },
    "name": "blind_review_package"
  }
}

Input Schema

NameRequiredDescriptionDefault
factsNo
personaNo
chaptersYes
platformNoqimao
include_promptsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

B3.1/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 disclosure, and it does deliver the most important trait: existing review fields are explicitly stripped, which is the blinding guarantee. It says nothing about whether anything is written to disk, what the returned payload looks like, or how persona/facts/platform alter the package, leaving real gaps for a no-annotation tool.

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

Conciseness4/5

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

A single dense sentence that front-loads the tool's identity and its defining constraint (stripping existing reviews). The internal 'P2c' tag is opaque but costs little; nothing else is wasted.

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 5-parameter tool with zero schema coverage, no annotations, and no output schema, one sentence is thin. The agent still cannot tell what the returned package contains structurally, what the default platform implies, or how facts/persona steer the output.

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% across 5 parameters, so the description must compensate and largely does not. It maps only '正文' to chapters and '提示词' to include_prompts, leaving facts, persona, and platform (including the 'qimao' default) completely unexplained.

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 concrete content ('正文+提示词') and a concrete exclusion ('显式剔除既有评审字段'), so the agent understands this assembles a blind input package rather than performing a review. It is clear on the resource but never names a sibling (blind_review, blind_compare) to distinguish when this packaging step is preferable.

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?

The phrase '供独立评审员产出 judgements' implies the downstream consumer (an independent reviewer) but not a when-to-use rule, prerequisite, or exclusion relative to blind_review/blind_compare. Usage is inferable from purpose rather than stated.

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