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

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

by proteus-vue

foreshadow_register

Registers foreshadowing items in a persistent, deduplicated ledger and tracks chapter indexes so overdue plot threads can be calculated.

Instructions

登记伏笔到持久化台账(去重);chapter_index 用于超期计算。

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_register"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemsYes
chapter_idYes
chapter_indexNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

C2.9/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does disclose two real behavioral traits beyond the schema: writes go to a persistent ledger and duplicates are handled (dedup), and chapter_index is consumed by overdue calculations rather than merely stored. It stops short of saying how dedup is decided (by text? by chapter?), whether duplicates are silently skipped or reported, or what a write failure looks like.

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 short clauses, front-loaded with the action and ledger persistence, with the parameter note second. Nothing is wasted, but the extreme terseness is partly the source of the missing semantics rather than pure efficiency.

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 mutation tool with no annotations, no output schema, and 0% schema coverage over three parameters, the definition is thin: it never says what items contain, how duplicates are reported, or what the call returns (e.g., created vs skipped entries). The overdue linkage is a useful fragment, but not enough to call this complete.

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 the description must compensate for all three parameters, and it explains only chapter_index (used for overdue computation). chapter_id and especially items (an array of strings) are left with no meaning in either the schema or the description, so an agent cannot tell whether items are foreshadowing texts, IDs, or labels.

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 verb ('register to a persistent ledger') plus a resource ('foreshadowing') and adds a scope note on deduplication, which separates it from the read/list siblings such as foreshadow_list and foreshadow_overdue. It does not explicitly name a sibling it is not, but the write-to-ledger framing is clear enough to pick out the tool's job.

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 guidance on when to call this tool versus foreshadow_close, foreshadow_list, or foreshadow_overdue; the only hint is the parenthetical 'deduplication' and the note that chapter_index feeds overdue computation. An agent must infer that this is the creation/registration step before closing or listing, rather than learning it from the definition.

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