Skip to main content
Glama

next_chapter_brief

Turns prior chapter review results, unresolved foreshadowing, persona anchors, and platform notes into next-chapter writing constraints plus a ready-to-use drafting prompt.

Instructions

【P1 闭环·零 LLM】评审回流:把上轮评审结论 + 未收伏笔 + 人设锚 + 平台档案转成下一章写作约束块,含可直接喂写稿 Agent 的 prompt(确定性转写,不新增判断;桩模式会明确标注)。

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": {
      "review": "<review>"
    },
    "name": "next_chapter_brief"
  }
}

Input Schema

NameRequiredDescriptionDefault
reviewYes上轮 review_chapter / review_batch 报告
personaNo
platformNo
project_idNo
chapter_indexNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.2/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. It usefully discloses that the transcription is deterministic, adds no new judgments, and that stub mode is explicitly marked — meaningful behavioral context. It does not cover whether the tool writes files or has side effects, error handling for a malformed review object, or permission requirements.

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, front-loaded sentence with no padding; the bracketed tag and the purpose follow immediately. It is dense with useful terms but earns its place, with only mild jargon overhead from 'P1 闭环·零 LLM'.

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 five-parameter tool with a nested required object and no output schema, the description says what is produced (constraint block + prompt) but not the output format or how the review object must be structured. It also does not explain default behavior when persona, platform, or chapter_index are omitted, leaving moderate gaps.

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 20%, and the description offers minimal compensation: '人设锚' loosely maps to persona and '平台档案' to platform, but project_id and chapter_index remain unexplained in both schema and description. The critical nested 'review' parameter's expected shape is only hinted at ('上轮 review_chapter / review_batch 报告'), leaving the agent to infer the structure.

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 states a specific transformation: it converts the previous round's review findings, unresolved foreshadowing, persona anchor, and platform profile into a next-chapter writing constraint block plus a ready-to-feed prompt. This is concrete and distinguishable from planning-oriented siblings, though it never names an alternative tool to sharpen the contrast.

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 prefix '评审回流' and the input '上轮评审结论' imply the tool is used after a review step, before drafting the next chapter. However, it does not explicitly say when to call this versus plan_chapter or review_chapter, nor does it state prerequisites or when not to use it.

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