Skip to main content
Glama

init_project

Creates a novel-writing project and records required positioning decisions—platform, audience, emotional contract, hook type, villain type, and differentiation—to start a constrained book pipeline.

Instructions

【定位层】开新书第 1 步:填定位决策卡并创建项目。 必填:项目id/项目名/书名/平台/受众/性别向/情感契约/改编形态/爽点类型/反派类型/差异化(缺任一即报错,补丁1-3)。 爽点类型五选一:打脸碾压 | 解谜智性 | 无声反杀 | 清醒退出 | 情感共鸣。 反派类型三选一:敌人(可打倒) | 规则(可理解) | 结构(不可打倒只能离开)。 调性 tone:冷感 | 炸裂 | 通用(决定感叹号禁用与字数区间预设)。

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>",
      "项目名": "<项目名>",
      "书名": "<书名>",
      "平台": "<平台>",
      "受众": "<受众>",
      "性别向": "<性别向>",
      "情感契约": "<情感契约>",
      "改编形态": "<改编形态>",
      "爽点类型": "<爽点类型>",
      "反派类型": "<反派类型>",
      "差异化": "<差异化>"
    },
    "name": "init_project"
  }
}

Input Schema

NameRequiredDescriptionDefault
toneNo调性预设
prefixNo伏笔编号前缀,默认 F;项目间必须独立(防串味)
书名Yes
受众Yes
平台Yes
差异化Yes
性别向Yes
项目名Yes
project_idYes
代入门槛No
反派类型Yes
对标作品No
情感契约Yes
改编形态Yes
日更计划No
核心情绪No
爽点类型Yes
目标体量No

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 does disclose two real behaviors: missing required field → error, and tone drives exclamation-mark prohibition and word-count presets. It omits idempotency/overwrite behavior on an existing project_id and says nothing about what is returned, which matter for a creation call.

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?

Front-loaded with the layer tag and step number, then the required-field checklist, then the two enum lists. Dense but every clause carries constraint information; no filler sentences.

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 an 11-required-param creation tool with no annotations and no output schema, the description covers validation and the three most decision-heavy fields but is silent on the optional positioning fields and on what a successful creation returns. Adequate to call correctly on required fields, incomplete for full parameter use.

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 only 11% across 18 params, so compensation is needed. The description does add real meaning for three fields — the five allowed 爽点类型 values, the three 反派类型 values, and what tone controls — but leaves the seven optional params (代入门槛, 目标体量, 核心情绪, 日更计划, 对标作品, etc.) and their intent entirely undocumented.

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 action-plus-resource: '开新书第 1 步:填定位决策卡并创建项目' — the agent knows this creates a project from a positioning card. The '第 1 步' framing situates it in the new-book workflow relative to sibling checks, though no sibling is named explicitly.

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?

Implied usage is clear (starting a new book, step 1), and it warns that any missing required field causes an error. It never says what to do if the project already exists, nor which sibling (save_card, save_outline, plan_chapter) should follow, so the agent must infer the rest of the workflow.

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