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

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

by proteus-vue

foreshadow_overdue

Detect unresolved foreshadowing that has exceeded its allowed age, optionally using max age and current chapter index. Returns an empty result when chapter order is unavailable rather than guessing.

Instructions

超期未收伏笔提醒;无章序信息时不臆断,返回空。

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "foreshadow_overdue"
  }
}

Input Schema

NameRequiredDescriptionDefault
max_ageNo
current_chapter_indexNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

B3.2/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full disclosure burden. It does contribute one non-obvious behavioral fact: the tool refuses to infer ordering and returns an empty result rather than fabricating an answer. It stops short of stating whether the operation is read-only, what the result shape is, or how 'overdue' is computed (presumably relative to max_age or chapter index).

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 tight clauses with the core purpose front-loaded and the edge-case rule second; nothing is padded or redundant. The brevity is efficient, though it shades into under-specification given the undocumented parameters.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-optional-parameter read tool with no output schema, the description covers the essential failure mode but omits parameter meaning and return contents. It is adequate to attempt a call, but not complete enough to call it correctly with confidence.

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% for both parameters, so the description must compensate and largely fails. The phrase '无章序信息' faintly gestures at current_chapter_index, but max_age is never mentioned at all — no units, no interpretation, no default behavior — leaving an agent unable to predict how either argument changes the output.

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 resource and function: it surfaces foreshadowing threads that are overdue for payoff ('超期未收伏笔提醒'). An agent can grasp what it retrieves without opening the schema. It does not, however, differentiate itself from the adjacent foreshadow_list or foreshadow_close tools, so the agent must guess which of the foreshadow family to call.

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?

It gives one conditional behavior rule — when no chapter-order information exists, do not guess and return empty — which is genuinely useful guidance about a degenerate case. But it never states when to prefer this over foreshadow_list or foreshadow_close, nor what prerequisites (e.g., a known current chapter) make the call meaningful, so usage is only implied.

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