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

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

by proteus-vue

foreshadow_close

Marks matching open foreshadow ledger entries as closed for a chapter, using text matches and optional evidence to keep narrative continuity tracking accurate.

Instructions

回收伏笔:按文本匹配把台账 open 条目标记为 closed。

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": {
      "chapter_id": "<chapter_id>",
      "items": "<items>"
    },
    "name": "foreshadow_close"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemsYes
evidenceNo
chapter_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

C2.8/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 behavioral burden for a mutation tool. It states the state transition (open → closed) but says nothing about what happens when text matching finds zero or multiple entries, whether closed entries can be reopened, whether the call is idempotent, or whether an error is raised on partial matches. That leaves the agent guessing about failure modes before writing to the ledger.

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 operation and matching mechanism front-loaded; nothing is redundant. It is tight rather than padded, though the terseness contributes to the disclosure gaps noted elsewhere.

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?

This is a low-complexity tool with only three parameters and no output schema, so a short description is defensible, and the core state transition is conveyed. However, with zero annotation coverage and zero schema descriptions, the definition should say more about matching behavior and results than it does for an agent to call it safely.

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 all three parameters are bare titles. The phrase '按文本匹配' hints that items are the strings to match against ledger entries, but it does not specify exact vs. substring vs. fuzzy matching, case sensitivity, or whether one item may resolve several entries. chapter_id and the optional evidence parameter are entirely unexplained.

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: it marks ledger entries that are in 'open' state as 'closed', and it names the mechanism ('按文本匹配', text matching). That is enough to distinguish it from siblings like foreshadow_register (which presumably creates entries) and foreshadow_list/foreshadow_overdue (reads). It stops short of explicitly naming those siblings, so it is clear but not sibling-differentiating.

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 statement of when to call this versus foreshadow_list or foreshadow_register, no prerequisite such as the entry having been registered first, and no note on whether this should be invoked at chapter completion. The word '回收' (payoff/resolve) only weakly implies the narrative moment for use.

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