Skip to main content
Glama

fanqie_imitation_score

Score trending novels on six imitation-fit dimensions to rank the best books for modeling. Get breakdowns for completion, length, heat, theme, tropes, and golden finger; switch to male serialized mode.

Instructions

【核心】仿写选书六维评分(完结度/体量适配/单本热度/题材吸量/套路密度/金手指清晰 + 稳定性/跨榜/巅峰加成)。也可切男频连载母本评分。用于在读爆款里筛出'最适合仿写'的书,并给出每本的分数拆解。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
topNo返回评分 Top N
rankNoread
serialNotrue=男频连载母本评分(连载体量×在读×更新活跃×吸量×套路×金手指)
channelNofemale

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.5/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the behavioral burden. It discloses that scores come from a six-dimension formula plus bonuses and explains the serial-mode formula ('连载体量×在读×更新活跃×吸量×套路×金手指'). However, it does not state whether output is sorted, what the score range or format is, or whether there are side effects, which is a notable gap for a tool with no annotations and no output schema.

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?

Two dense sentences front-load the core purpose and then give the mode variant and intended use. Every sentence adds information, though the slash-separated jargon list ('套路密度/金手指清晰') makes the description slightly harder to parse.

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?

Moderate complexity with four optional parameters, no annotations, and no output schema requires more detail about the score breakdown, sorting, and how rank/channel map to the modes. The description explains the 'why' and scoring dimensions, but an agent would still be guessing about the return shape and the meaning of two parameters.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 50%: top and serial have descriptions, while rank and channel are bare enums. The description adds meaning to serial mode and to the scoring dimensions, and implies female as the default by mentioning male serial mode as a switch, but it does not explain rank (read/new/completed) or channel (female/male). The description compensates partially but not fully.

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 concrete operation ('仿写选书六维评分') and identifies the resource ('在读爆款') and output ('给出每本的分数拆解'), so an agent can understand the purpose. It does not explicitly distinguish itself from sibling tools like fanqie_ranks or fanqie_trend, but the scoring focus is distinctive enough to avoid confusion.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It states the intended scenario ('用于在读爆款里筛出最适合仿写的书') and provides a conditional mode switch ('也可切男频连载母本评分'), which gives usable context. It does not name alternatives or say when not to use this tool instead of fanqie_find or fanqie_stats.

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