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

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

by proteus-vue

foreshadow_list

Lists foreshadowing ledger entries filtered by open, closed, or all status, helping reviewers track unresolved plot threads during novel submission review.

Instructions

查看伏笔台账:status=open|closed|all。

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

Input Schema

NameRequiredDescriptionDefault
statusNoopen

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?

With no annotations provided, the description carries the full burden and does little: 'view' implies a read operation, but nothing is said about permissions, whether the result is paginated or bounded, or what happens with the default state. It discloses essentially only the read-only nature.

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?

One short line, front-loaded with the resource and followed immediately by the parameter values. Nothing is wasted, though it is arguably too terse to be maximally useful.

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 single-parameter list tool with no output schema and no annotations, the definition covers the basic call but leaves the return shape and result scope undescribed. It is minimally sufficient to invoke but not to predict what comes back.

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 0% and the schema declares no enum, so the description's 'status=open|closed|all' is genuinely additive — it supplies the allowed values that the schema omits. However it does not explain what 'all' includes or how the default 'open' behaves, leaving it a partial compensation.

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 specific verb ('查看' / view) and resource ('伏笔台账' / foreshadowing ledger), which clearly identifies this as the read/list operation among the foreshadow siblings. It does not explicitly name foreshadow_close or foreshadow_overdue as the alternatives, but the listing purpose is unmistakable.

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 use this versus foreshadow_overdue, foreshadow_register, or foreshadow_close, and no prerequisites or exclusions. The only usage signal is implicit in 'view the ledger'.

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