Skip to main content
Glama

save_outline

Save chapter-by-chapter outlines while validating title rules and foreshadowing references—resolved threads must already be planted, and new clue numbering conflicts are flagged.

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>",
      "chapter_no": "<chapter_no>",
      "title": "<title>",
      "dark_point": "<dark_point>"
    },
    "name": "save_outline"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleYes
emotionNo
summaryNo
word_typeNo
chapter_noYes
dark_pointYes暗爽点(本章爽点在哪)
project_idYes项目 ID(内部代号,如“默者”)
foreshadow_newNo
foreshadow_resolveNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose meaningful behavior beyond the schema: automatic chapter-title validation and foreshadow-reference checks (resolved entries must be already planted and unresolved; duplicate new-plant numbers trigger a warning). It stops short of saying whether failures block the save or merely warn, and says nothing about permissions or persistence.

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?

Two compact sentences with the purpose stated first and the validation behavior second; every clause carries information. The bracketed layer tag is a minor overhead but useful for categorization.

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?

For a 9-parameter write tool with no annotations, no output schema, and low schema coverage, the description covers the validation behavior well but leaves most parameter meanings and the failure/return behavior unexplained. It is adequate but not sufficient for confident invocation.

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 only 22% across 9 parameters, so the description must compensate, and it partly does by implying the title parameter (章名合规) and giving real semantics for foreshadow_resolve/foreshadow_new (planted-state constraints, numbering conflicts). The emotion, summary, word_type, and chapter_no parameters receive no explanation anywhere, leaving a substantial gap.

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 names a specific verb and resource — "保存逐章章纲(施工图)" — and tags it as the structure layer, which distinguishes it from sibling artifact-savers like save_card or the planning tools. It is clear what is being written, though it does not explicitly contrast with plan_chapter or save_card.

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?

Usage is implied by "逐章" (one per chapter) and the structure-layer tag, so an agent can infer this is the write step for chapter outlines. However, there is no explicit when-to-use vs. plan_chapter, no statement of prerequisites (e.g., project must exist, prior chapters saved), and no when-not-to-use guidance.

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