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

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

by proteus-vue

platform_fit

Scores a manuscript against a target platform's submission preferences and lists the gaps, helping writers align a novel with platform expectations 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": "platform_fit"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYes
platformNoqimao

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

C2.9/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. It implies an analysis-only operation (score plus gap list), but it does not say whether the input text is modified, what the output looks like, how many platforms are supported, or whether scoring is deterministic, which leaves a mutation or read-only operation ambiguous.

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 front-loaded sentence with a label prefix and no filler, so nothing is wasted. Its brevity is efficient, though it borders on being too sparse for a scoring tool with undocumented parameters.

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 that performs preference-based scoring, with no annotations, no output schema, and zero parameter documentation, the description is far too thin. An agent still lacks the valid platform values, the expected input shape, and any sense of what the gap list contains.

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 coverage is 0% across two parameters. The description hints at a target platform (mapping to the platform parameter) but never says what the required text parameter represents, nor does it enumerate valid platform values; the schema shows a default of "qimao" but no enum, so the description should have compensated and does not.

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 gives a concrete verb and object: score the text against a target platform's submission preferences and list the gaps. That is more than a restatement of the name, but it never distinguishes this from siblings such as benchmark or blind_review, so an agent cannot tell from the text alone which of these evaluation tools to pick.

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 "按目标平台收稿偏好" implies the usage context, namely checking a manuscript before submitting to a particular platform, but it never says when to choose this over benchmark or blind_review, and it states no prerequisites or exclusions. Guidance is only implied.

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