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

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

by proteus-vue

blind_validate_judgements

Validate the structure and scoring criteria of external blind review JSON. Does not supplement scores or auto-convert values.

Instructions

校验外部盲评 JSON 的结构与评分口径;不补分、不自动换算。

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>",
      "judgements": "<judgements>"
    },
    "name": "blind_validate_judgements"
  }
}

Input Schema

NameRequiredDescriptionDefault
chaptersYes
judgementsYes

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 carries the full behavioral burden. It does disclose two meaningful constraints — it will not fill in missing scores (不补分) and will not auto-convert score scales (不自动换算) — which is real value beyond structured fields. But it says nothing about whether the tool is read-only, what happens on invalid input (error vs. a report), or what the validation result contains, and there is no output schema to cover that.

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 compact sentence with the core purpose front-loaded and the two negative constraints appended after a semicolon. Nothing is wasted, though the terseness leaves the payload structure entirely unaddressed.

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 tool with two required, nested, zero-documented parameters, no annotations, and no output schema, the description is too thin. It never describes the expected JSON shape, the scoring-rubric rules being enforced, or the form of the validation result, which are exactly the gaps structured fields leave open.

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 both parameters (chapters as an array of free-form objects, judgements as a free-form object) are nested and untyped. The description never explains what belongs in chapters versus judgements, nor the expected shape of the blind-review JSON, so an agent must guess at the payload structure.

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 a specific verb and object: validate the structure and scoring rubric of external blind-review JSON. The word 'external' (外部) implicitly separates it from the sibling review tools (blind_review, blind_compare), which produce reviews rather than check them, though no sibling is named explicitly.

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 implied by 'external blind-review JSON' — an agent can infer this is the check step for JSON produced elsewhere. However, there is no explicit when-to-use/when-not guidance, no mention of what to do when validation fails, and no pointer to a sibling for the case where the agent needs a review generated rather than validated.

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