Skip to main content
Glama

touch_foreshadow

Records chapter-specific mentions of long-term foreshadowing to track activity and support health checks in novel-writing projects.

Instructions

【结构层】记录长线伏笔"呼吸"(提及章号),用于健康度检查。

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>",
      "id": "<id>",
      "chapter": "<chapter>"
    },
    "name": "touch_foreshadow"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.9/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 behavioral burden and it does not meet it. It says nothing about whether repeated touches in the same chapter are deduplicated or overwrite, whether the foreshadow id must already exist, what happens on an unknown id, or what the call returns.

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 sentence with the layer tag front-loaded and no filler. It is efficient, though the bracketed 【结构层】 tag and the quoted 呼吸 metaphor consume space without adding operational meaning.

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 3-required-parameter mutation tool with no annotations, no output schema, and low schema coverage, the description is too thin. It omits the effect on project state, idempotency, error behavior, and any hint of what the health-check consumer expects, leaving the agent to guess at invocation semantics.

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 only 33%: project_id is documented in the schema, but id and chapter are bare. The description partially compensates by stating that chapter is the 提及章号 that is being recorded, yet it never explains what id refers to (a foreshadow identifier) or its expected format, and it does not cover project_id's role at all.

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 (记录, record) and a specific resource (长线伏笔"呼吸", a long-line foreshadowing "breath") plus the payload (提及章号, the chapter number of the mention), so an agent can infer this marks an existing foreshadow as touched in a given chapter. The metaphor "呼吸" is project jargon rather than a plain statement of effect, and it does not name how it differs from add_foreshadow, which keeps it from 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 Guidelines3/5

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

The trailing clause "用于健康度检查" signals the downstream purpose, so the agent can infer this is the tracking call that feeds health analysis. However, there is no explicit when-to-use versus when-not guidance and no mention of the sibling tools (add_foreshadow, resolve_foreshadow, foreshadow_health) that an agent must choose between.

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