Skip to main content
Glama

plan_chapter

Generates a chapter outline template with word-count-type ranges, excitement-point density rules, and event-library rotation reminders to support consistent chapter planning.

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>",
      "word_type": "<word_type>"
    },
    "name": "plan_chapter"
  }
}

Input Schema

NameRequiredDescriptionDefault
word_typeYes字数类型:静场/常规/反击/高潮/极短
chapter_noYes
project_idYes项目 ID(内部代号,如“默者”)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations, the description carries the burden of behavioral disclosure. It usefully states that the generated outline uses a floating range rather than a fixed number and includes density rules and rotation reminders. However, it does not clarify whether the template is returned only or saved into the project, nor does it describe side effects, permissions, or failure behavior.

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?

The description is a single dense sentence with no wasted wording. The purpose and key output elements are front-loaded and easy to scan. The bracketed layer tag provides useful context without bloating the definition.

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 three-parameter generation tool with no annotations and no output schema, the description covers the core output components reasonably well. It still leaves important gaps around whether the generated template is persisted, what exact structure is returned, and how chapter_no affects the result. It is adequate but not complete.

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 coverage is 67%, with project_id and word_type documented in the schema but chapter_no undocumented. The description adds meaning for word_type by explaining that it drives the floating range, density rules, and rotation reminders. It does not compensate for the missing chapter_no semantics or clarify project_id beyond the schema.

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 a concrete resource, 某章的章纲模板, so the core action is clear. It also specifies the template's contents: floating range by word-count type, excitement-point density rules, and event-library rotation reminders. It does not explicitly distinguish itself from siblings such as save_outline, so it falls short of 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 Guidelines2/5

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

The description gives no explicit when-to-use or when-not-to-use guidance. The 【结构层】 tag hints at a planning phase, but it does not name alternatives or state prerequisites. An agent must infer the workflow context from the tool name and description alone.

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