Skip to main content
Glama

foreshadow_list

Lists a novel project's foreshadowing ledger and filters open, closed, or all items so writers can track unresolved setup and payoff threads.

Instructions

查看项目伏笔台账(对齐 novel-review-mcp 的工具名)。

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": {
      "project_id": "<project_id>"
    },
    "name": "foreshadow_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
statusNo
project_idYes项目 ID(内部代号,如“默者”)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.4/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 disclosure burden. "查看" weakly implies a read-only operation, but there is no mention of ordering, pagination, empty-ledger behavior, or what a ledger entry looks like — all of which matter for an agent deciding whether to call it.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single short, front-loaded sentence with no padding in the functional clause. But roughly half the text is a note about matching an external MCP's tool naming, which does no work for an agent selecting or invoking the tool.

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 simple two-parameter read tool with no output schema and no annotations, the description should at minimum define the status filter semantics and what the ledger returns. Neither is present, leaving the one undescribed parameter ambiguous at call time.

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 coverage is 50%: project_id is documented in the schema, but the status enum (open/closed/all) has no description anywhere. The description adds nothing about what these filters mean (e.g., whether "open" means unresolved foreshadows), so it fails to compensate for the coverage gap.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description pairs the verb "查看" (view) with the resource "项目伏笔台账" (project foreshadow ledger), so the basic function is inferable. However, it never states that this returns a *list* of foreshadows or how that differs from siblings like foreshadow_health and foreshadow_overdue, which also read foreshadow data. The parenthetical about name alignment is meta-information, not purpose.

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 pick this tool over foreshadow_health, foreshadow_overdue, or extract_foreshadow. Nothing tells the agent whether this is the full inventory versus a filtered subset, so selection among the read-oriented siblings is left entirely to inference.

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