Skip to main content
Glama

foreshadow_health

Audit foreshadowing health at chapter checkpoints by calculating recovery rates, listing pending clues, and flagging spontaneous recoveries.

Instructions

【结构层】伏笔健康度检查(每 10 章一次 / 每卷群结束必查):回收率、待回收清单、长线呼吸、凭空回收统计。

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>",
      "current_chapter": "<current_chapter>"
    },
    "name": "foreshadow_health"
  }
}

Input Schema

NameRequiredDescriptionDefault
project_idYes项目 ID(内部代号,如“默者”)
current_chapterYes当前写到第几章

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.8/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 behavioral burden. It discloses the computed outputs, which implies a read-only diagnostic, but never states that it is non-mutating, what permissions it needs, or how expensive the scan is.

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

Conciseness5/5

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

One dense sentence that front-loads the layer tag, then the cadence rule, then the reported metrics. No filler or redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter, non-nested tool with no output schema, enumerating the four reported metrics compensates well for the missing return-value documentation. Only the read-only nature and any cost/scope caveats remain unstated.

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 100% and both parameters (project_id, current_chapter) are documented in the schema itself. The description adds no meaning beyond the schema, so the baseline 3 applies.

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 a specific resource and action: a foreshadowing health check that reports recovery rate, pending-recovery list, long-line breathing, and out-of-nowhere recovery stats. This aggregate diagnostic is distinguishable from sibling CRUD tools like add_foreshadow or resolve_foreshadow, though no sibling is named explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides an explicit cadence trigger: once every 10 chapters, and mandatory at the end of each volume group. That is real when-to-use guidance, but it names no alternatives (e.g., foreshadow_overdue for a narrower overdue check) and gives no when-not-to-use condition.

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