Skip to main content
Glama

Novel Save Management

manage_novel
Destructive

Create, resume, switch, end, rename, and list novels while saving or retrieving play context. Record provenance and filter active or archived campaigns for persistent lifecycle management.

Instructions

Manage a Novel's save-file lifecycle: create, resume, switch, end, rename, describe, set genre, list, save/get play context, and record provenance. list returns one line per Novel unless detail is set, and filter selects active, archived, or all. create, save_context, and provenance persist; list, info, and get_context are read-only. export, import, archive/unarchive, clone/branch, and checkpoint actions remain callable here for compatibility, but manage_archive exposes them with clearer scope — prefer it. Lifecycle changes are not reversible via manage_history, so clone a Novel before a risky change. Use when: handling a campaign's lifecycle or returning to saved context. Do NOT use when: managing content inside the Novel — use the entity tools; use manage_archive for export, import, archiving, cloning, branching, and checkpoints.

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": {
      "action": "<action>"
    },
    "name": "manage_novel"
  }
}

Input Schema

NameRequiredDescriptionDefault
dataNoExported Novel JSON (import).
modeNodry-run, merge, or replace (import).
nameNoNovel name (create).
slugNoNovel slug (resume/switch/archive/unarchive/info).
genreNoGenre tag (create/genre).
labelNoCheckpoint label (checkpoint_set/list/restore/remove).
scopeNoExport scope (export).
shareNoEmit a portable full-scope bundle with embedded adventure content (export; JSON only).
actionYescreate, resume, switch, end, export, import, rename, description, list, archive, unarchive, info, genre, complete_session_zero, clone, branch, save_context, get_context, checkpoint_set, checkpoint_list, checkpoint_restore, checkpoint_remove, or provenance.
detailNoReturn full metadata (list).
filterNoactive, archived, or all (list).
formatNoOutput format (export).
strictNoFail on any cross-reference mismatch (import).
creatorNoCreator attributed on the Novel's provenance record (provenance).
licenseNoLicense declared on the Novel's provenance record (provenance).
rulesetNoRuleset slug (create).
new_nameNoName for the copy or branch (clone/branch).
new_slugNoNew slug (rename).
from_eventNoEvent-log ordinal to branch from (branch; default latest).
attributionNoSource attributed on the Novel's provenance record (provenance).
descriptionNoDescription (create/description).
source_slugNoNovel to copy or branch from (clone/branch).
player_goalsNoPlayer goals (save_context).
current_sceneNoCurrent-scene summary (save_context).
codex_adventureNoCodex adventure to seed from (create).
long_term_plansNoLong-term plans (save_context).
short_term_plansNoShort-term plans (save_context).
immediate_situationNoImmediate situation (save_context).
include_checkpointsNoInclude checkpoints in export (default false; export).
trim_audit_sessionsNoKeep only the most recent N sessions' audit entries in the clone (clone; default full copy).
pending_player_actionNoPending player action (save_context).

Output Schema

NameRequiredDescriptionDefault
textNoHuman-readable text envelope mirroring the structured result (REQ-001, REQ-548a).
statusYesMachine-readable result status: OK, NEED_INPUT, WARNING, PARTIAL, or an error category (REQ-002, REQ-548c).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv2026.10.18
    • changedInput schema / properties / action / description
      Previous value: -"create, resume, switch, end, export, import, rename, description, list, archive, unarchive, info, genre, complete_session_zero, clone, branch, save_context, get_context, checkpoint_set, checkpoint_list, checkpoint_restore, or checkpoint_remove."New value: +"create, resume, switch, end, export, import, rename, description, list, archive, unarchive, info, genre, complete_session_zero, clone, branch, save_context, get_context, checkpoint_set, checkpoint_list, checkpoint_restore, checkpoint_remove, or provenance."
    • changedInput schema / properties / action / enum
      Previous value: -[
      -  "create",
      -  "resume",
      -  "switch",
      -  "end",
      -  "rename",
      -  "description",
      -  "list",
      -  "info",
      -  "genre",
      -  "complete_session_zero",
      -  "save_context",
      -  "get_context"
      -]New value: +[
      +  "create",
      +  "resume",
      +  "switch",
      +  "end",
      +  "rename",
      +  "description",
      +  "list",
      +  "info",
      +  "genre",
      +  "complete_session_zero",
      +  "save_context",
      +  "get_context",
      +  "provenance"
      +]
    • addedInput schema / properties / attribution
      Added value: +{
      +  "description": "Source attributed on the Novel's provenance record (provenance).",
      +  "type": "string"
      +}
    • addedInput schema / properties / creator
      Added value: +{
      +  "description": "Creator attributed on the Novel's provenance record (provenance).",
      +  "type": "string"
      +}
    • addedInput schema / properties / license
      Added value: +{
      +  "description": "License declared on the Novel's provenance record (provenance).",
      +  "type": "string"
      +}
    • addedInput schema / properties / share
      Added value: +{
      +  "description": "Emit a portable full-scope bundle with embedded adventure content (export; JSON only).",
      +  "type": "boolean"
      +}
  2. Changed1 schema field changed
    • changedInput schema / properties / action / enum
      Previous value: -[
      -  "create",
      -  "resume",
      -  "switch",
      -  "end",
      -  "export",
      -  "import",
      -  "rename",
      -  "description",
      -  "list",
      -  "archive",
      -  "unarchive",
      -  "info",
      -  "genre",
      -  "complete_session_zero",
      -  "clone",
      -  "branch",
      -  "save_context",
      -  "get_context",
      -  "checkpoint_set",
      -  "checkpoint_list",
      -  "checkpoint_restore",
      -  "checkpoint_remove"
      -]New value: +[
      +  "create",
      +  "resume",
      +  "switch",
      +  "end",
      +  "rename",
      +  "description",
      +  "list",
      +  "info",
      +  "genre",
      +  "complete_session_zero",
      +  "save_context",
      +  "get_context"
      +]
  3. Changed2 schema fields changedv2026.10.12
    • changedInput schema / properties / action / description
      Previous value: -"create, resume, switch, end, export, import, rename, description, list, archive, unarchive, info, genre, clone, branch, save_context, get_context, checkpoint_set, checkpoint_list, checkpoint_restore, or checkpoint_remove."New value: +"create, resume, switch, end, export, import, rename, description, list, archive, unarchive, info, genre, complete_session_zero, clone, branch, save_context, get_context, checkpoint_set, checkpoint_list, checkpoint_restore, or checkpoint_remove."
    • changedInput schema / properties / action / enum
      Previous value: -[
      -  "create",
      -  "resume",
      -  "switch",
      -  "end",
      -  "export",
      -  "import",
      -  "rename",
      -  "description",
      -  "list",
      -  "archive",
      -  "unarchive",
      -  "info",
      -  "genre",
      -  "clone",
      -  "branch",
      -  "save_context",
      -  "get_context",
      -  "checkpoint_set",
      -  "checkpoint_list",
      -  "checkpoint_restore",
      -  "checkpoint_remove"
      -]New value: +[
      +  "create",
      +  "resume",
      +  "switch",
      +  "end",
      +  "export",
      +  "import",
      +  "rename",
      +  "description",
      +  "list",
      +  "archive",
      +  "unarchive",
      +  "info",
      +  "genre",
      +  "complete_session_zero",
      +  "clone",
      +  "branch",
      +  "save_context",
      +  "get_context",
      +  "checkpoint_set",
      +  "checkpoint_list",
      +  "checkpoint_restore",
      +  "checkpoint_remove"
      +]
  4. Addedv1.0.3

TDQS

A4.3/5.0
Behavior4/5

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

Beyond the annotations, the description classifies actions by persistence (create/save_context/provenance persist; list/info/get_context are read-only) and warns that lifecycle changes are not reversible via manage_history, which is actionable risk context matching destructiveHint=true. It does not cover what 'end' actually does to a Novel or any output/permission constraints, so it stops short of fully rich disclosure.

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 lifecycle purpose, then persistence classification, then the sibling routing warning, then explicit Use/Do-NOT-use blocks — easy to scan. It loses a little efficiency by re-listing action names that already appear in the schema enum, but every other sentence carries routing or risk information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 31-parameter, multi-action tool with an output schema (so return shape needn't be explained), the description covers purpose, per-action read/write nature, irreversibility, and sibling routing. It is slightly incomplete on the semantics of less-obvious actions such as end and complete_session_zero, but the essentials for correct invocation are present.

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 100%, so the baseline is 3. The description adds genuine meaning for two parameters only — 'detail' (one line per Novel unless set) and 'filter' (active/archived/all) — while data, mode, share, scope, format, strict, and from_event are left entirely to their schema descriptions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a concrete resource (a Novel's save-file lifecycle) and enumerates the specific operations: create, resume, switch, end, rename, describe, set genre, list, save/get play context, provenance. It also explicitly separates itself from the two nearest siblings (entity tools for content, manage_archive for export/import/archive/clone/checkpoint), so an agent can route correctly without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

It gives explicit when-to-use ('handling a campaign's lifecycle or returning to saved context') and when-not-to-use ('managing content inside the Novel — use the entity tools'), plus a concrete preferred alternative for the compatibility actions: 'manage_archive exposes them with clearer scope — prefer it.' Nothing about selection is left to inference.

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