Skip to main content
Glama

foreshadow_overdue

Identify overdue unresolved foreshadowing in a novel project so writers can close plot threads. Returns an empty result when chapter order is unavailable instead of guessing.

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

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3/5.0
Behavior3/5

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

With no annotations at all, the description carries the full burden. It usefully discloses one real behavioral trait, that the tool refuses to infer overdue status without chapter-order data and returns empty instead, which warns the agent off misreading an empty result as 'nothing overdue'. It says nothing about read-only nature, cost, or ordering of results.

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 clause front-loads the purpose, followed by the key caveat. No filler, though the parenthetical '(对齐 novel-review-mcp)' is an implementation note of little value to an agent choosing the tool.

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?

There is no output schema, so the description should at least indicate the shape of the reminder list; it does not. The parameter gap (max_age) and the absence of guidance about result ordering make it only minimally sufficient for a three-parameter query tool.

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 only 33%, and only project_id is documented in the schema. The description hints that current_chapter_index governs the empty-return behavior, but never names it, and max_age is left entirely unexplained in both schema and description, leaving the agent to guess its unit and effect.

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?

States the resource and the filtered scope precisely: unresolved foreshadows that are overdue (超期未收伏笔). An agent can tell it is a status/reminder query rather than a mutation. It does not, however, distinguish itself from siblings like foreshadow_health or foreshadow_list, so it stops short of a 5.

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?

The only conditional given ('when there is no chapter-order information, return empty rather than guessing') describes an internal fallback, not when an agent should choose this tool over foreshadow_health, foreshadow_list, or foreshadow_health. No use case, prerequisite, or exclusion is stated.

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