Skip to main content
Glama

add_foreshadow

Creates a foreshadowing record for a novel project using an ID, content, level, and planting chapter; rejects duplicate IDs and warns on repeated content.

Instructions

【结构层】新埋伏笔。id:单级用 F1/G1,两级(300万字+)用 L1 或 C3-1(第3卷群第1条)。 同名 id 已存在 → 报错;同内容重复埋设 → 冗余警告。

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>",
      "content": "<content>",
      "level": "<level>",
      "planted_at": "<planted_at>"
    },
    "name": "add_foreshadow"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes伏笔编号
noteNo
levelYesL=跨卷群长线 C=卷群内 F=单级编号
contentYes
planted_atYes埋设章号
project_idYes项目 ID(内部代号,如“默者”)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.5/5.0
Behavior3/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 it does disclose two real behavioral traits: a duplicate id raises an error, and re-planting identical content triggers a redundancy warning. That is genuinely useful pre-call knowledge. However, it says nothing about whether the write is reversible, what permissions or project state are required, or what a successful 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.

Conciseness5/5

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

Two compact sentences, front-loaded with the tool's purpose and layer, followed by the id convention and the two failure conditions. No filler and no redundancy.

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 six-parameter mutation tool with no annotations and no output schema, the definition should say more: content and note are undocumented in both schema and description, and there is no statement of side effects, validation rules for content, or what the caller gets back. The error/warning disclosure helps, but significant gaps remain for a write operation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 67%, leaving content and note undocumented, but the description compensates for the most important gap by explaining the id numbering scheme (single-level F/G vs. two-level L/C with volume-group prefixes), which the schema only labels as "伏笔编号". That is real added meaning beyond the schema rather than a restatement.

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 verb (plant) plus resource (foreshadow) and even names the layer ("【结构层】"), so an agent knows exactly what record is being created. It does not explicitly contrast itself with touch_foreshadow / resolve_foreshadow, but the "新" (new) qualifier makes the distinction largely inferable.

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 description supplies strong guidance on how to construct the id (F1/G1 for single-level, L1 or C3-1 for two-level works of 3M+ characters), which is really parameter-level usage guidance. It gives no explicit when-to-use / when-not-to-use rule relative to sibling tools such as touch_foreshadow or resolve_foreshadow, so usage is only implied.

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