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

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

by proteus-vue

benchmark

Scores novel text by structural density against a reference baseline and outputs the gap, helping identify platform-fit weaknesses before submission.

Instructions

对标头部:按结构密度维度打分,输出与头部基线的 gap。

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": "benchmark"
  }
}

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?

With no annotations at all, the description carries the full disclosure burden and delivers very little: it does not confirm this is a read-only/non-destructive analysis, does not say whether scoring is deterministic or model-driven, and gives no sense of cost, latency, or how long a text is acceptable. Only the phrase about outputting a gap hints at the return shape, which is too thin for an unannotated 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 compact sentence with the scoring action and the output front-loaded; nothing is padded or repetitive. It is efficient, though its brevity is also the source of the definition's underspecification.

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 analysis tool with no annotations, no output schema, and zero schema descriptions, the definition leaves the agent guessing about input granularity, baseline selection, and the form of the returned "gap". A reader could not confidently invoke it correctly without trial and error.

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 both parameters rely entirely on the description — yet it never mentions `text` (what granularity: a chapter, an outline, a full manuscript?) nor `platform` (default "qimao", clearly a baseline selector, entirely unexplained). The description adds almost no meaning beyond the bare schema.

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 an action (score by structural density) and an output (gap versus a top-tier baseline), so an agent can roughly tell this is an evaluation/benchmarking tool rather than a mutation tool. However, "对标头部" and "头部基线" are never grounded — it does not say which corpus or profile the baseline comes from — and nothing distinguishes it from nearby scoring tools such as platform_fit or blind_compare.

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 statement, no prerequisite or input expectation, and no reference to any alternative tool or when this should be chosen over platform_fit/blind_compare. The agent must infer applicability purely from the name.

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