holonovel

Lore Management

manage_lore

Destructive

Create, update, import, and export durable lore entries with recall triggers, priority, and player-visible knowledge controls for a Novel campaign.

Instructions

Manage the active Novel's lore entries — shared, durable world facts every caller recalls. set/update writes a keyed entry with recall triggers, priority, sticky weight, and a badge_scope (game_master hides it from the Player badge); set_secret, reveal, secret_list, and knowledge control Player-visible knowledge. import defaults to a non-mutating dry-run, while merge and replace write. Lore mutations require the GM or Editor badge, persist to the Novel, and are undoable via manage_history (action: undo); list, get, export, secret_list, and knowledge are read-only. Use when: creating, revising, removing, toggling, grouping, suggesting, listing, exporting, or importing lore, or controlling what an entity knows. Do NOT use when: recording one entity's beliefs or perceptions — use manage_belief; handling cold-reference corpus documents — use manage_corpus.

Input Schema

Name	Required	Description
`key`	No	Lore key (set/update/remove/toggle/group/get).
`data`	No	JSON or Markdown lorebook data (import).
`mode`	No	dry-run, merge, or replace (import).
`group`	No	Group name, or null to clear (set/update/group).
`action`	Yes	set, update, remove, toggle, group, suggest, list, get, export, import, set_secret, reveal, secret_list, or knowledge.
`detail`	No	Return full lore entries instead of summary entries (list).
`format`	No	Optional output format (export).
`sticky`	No	Optional sticky weight (set/update).
`content`	No	Lore content (set/update).
`priority`	No	Optional priority (set/update).
`triggers`	No	Optional recall triggers (set/update).
`entity_id`	No	Entity to reveal to / whose knowledge to read (reveal/knowledge).
`badge_scope`	No	game_master or shared (set/update).
`world_target`	No	Optional world-model target reference (set/set_secret).

Output Schema

Name	Required	Description	Default
`text`	No	Human-readable text envelope mirroring the structured result (REQ-001, REQ-548a).
`status`	Yes	Machine-readable result status: OK, NEED_INPUT, WARNING, PARTIAL, or an error category (REQ-002, REQ-548c).

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv2026.10.15Oct 25, 2026
- removedInput schema / properties / group / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedInput schema / properties / group / type
```
Added value: +[
+  "string",
+  "null"
+]
```

Changed14 schema fields changedv2026.10.13Oct 25, 2026

changedInput schema / properties / action / description

Previous value: -"Lore: set, update, remove, toggle, group, suggest, list, get, export, import, set_secret, reveal, secret_list, or knowledge. Corpus: corpus_register, corpus_list, corpus_get, corpus_route, corpus_grant, corpus_deny, corpus_access, corpus_consume, or corpus_acquisitions."New value: +"set, update, remove, toggle, group, suggest, list, get, export, import, set_secret, reveal, secret_list, or knowledge."

removedInput schema / properties / corpus_access_domains

Removed value: -{
-  "description": "Knowledge domains granted access (corpus_register).",
-  "items": {
-    "type": "string"
-  },
-  "type": "array"
-}

removedInput schema / properties / corpus_access_public

Removed value: -{
-  "description": "Whether every entity may consume it (corpus_register; default false).",
-  "type": "boolean"
-}

removedInput schema / properties / corpus_body

Removed value: -{
-  "description": "Document reference text (corpus_register).",
-  "type": "string"
-}

removedInput schema / properties / corpus_denies

Removed value: -{
-  "description": "Entity ids explicitly denied access (corpus_register).",
-  "items": {
-    "type": "string"
-  },
-  "type": "array"
-}

removedInput schema / properties / corpus_document_id

Removed value: -{
-  "description": "Corpus document id (corpus_get/corpus_route/corpus_grant/corpus_deny/corpus_consume).",
-  "type": "string"
-}

removedInput schema / properties / corpus_domain

Removed value: -{
-  "description": "Knowledge domain (corpus_register/corpus_route/corpus_list).",
-  "type": "string"
-}

removedInput schema / properties / corpus_domains

Removed value: -{
-  "description": "Knowledge domains the entity may access (corpus_access).",
-  "items": {
-    "type": "string"
-  },
-  "type": "array"
-}

removedInput schema / properties / corpus_entity_id

Removed value: -{
-  "description": "Entity acquiring or inspected (corpus_consume/corpus_acquisitions/corpus_access/corpus_grant/corpus_deny).",
-  "type": "string"
-}

removedInput schema / properties / corpus_grants

Removed value: -{
-  "description": "Entity ids explicitly granted access (corpus_register).",
-  "items": {
-    "type": "string"
-  },
-  "type": "array"
-}

removedInput schema / properties / corpus_mode

Removed value: -{
-  "description": "read, research, taught, or import (corpus_consume; default read).",
-  "enum": [
-    "read",
-    "research",
-    "taught",
-    "import"
-  ],
-  "type": "string"
-}

removedInput schema / properties / corpus_source_profile

Removed value: -{
-  "description": "Trusted source profile the domain is routed from (corpus_register; default manual).",
-  "type": "string"
-}

removedInput schema / properties / corpus_title

Removed value: -{
-  "description": "Document title (corpus_register).",
-  "type": "string"
-}

addedInput schema / properties / detail

Added value: +{
+  "description": "Return full lore entries instead of summary entries (list).",
+  "type": "boolean"
+}

Changed1 schema field changedOct 22, 2026

changedInput schema / properties / action / enum

Previous value: -[
-  "set",
-  "update",
-  "remove",
-  "toggle",
-  "group",
-  "suggest",
-  "list",
-  "get",
-  "export",
-  "import",
-  "set_secret",
-  "reveal",
-  "secret_list",
-  "knowledge",
-  "corpus_register",
-  "corpus_list",
-  "corpus_get",
-  "corpus_route",
-  "corpus_grant",
-  "corpus_deny",
-  "corpus_access",
-  "corpus_consume",
-  "corpus_acquisitions"
-]New value: +[
+  "set",
+  "update",
+  "remove",
+  "toggle",
+  "group",
+  "suggest",
+  "list",
+  "get",
+  "export",
+  "import",
+  "set_secret",
+  "reveal",
+  "secret_list",
+  "knowledge"
+]

Changed14 schema fields changedv1.0.5Oct 12, 2026

changedInput schema / properties / action / description

Previous value: -"set, update, remove, toggle, group, suggest, list, get, export, import, set_secret, reveal, secret_list, or knowledge."New value: +"Lore: set, update, remove, toggle, group, suggest, list, get, export, import, set_secret, reveal, secret_list, or knowledge. Corpus: corpus_register, corpus_list, corpus_get, corpus_route, corpus_grant, corpus_deny, corpus_access, corpus_consume, or corpus_acquisitions."

changedInput schema / properties / action / enum

Previous value: -[
-  "set",
-  "update",
-  "remove",
-  "toggle",
-  "group",
-  "suggest",
-  "list",
-  "get",
-  "export",
-  "import",
-  "set_secret",
-  "reveal",
-  "secret_list",
-  "knowledge"
-]New value: +[
+  "set",
+  "update",
+  "remove",
+  "toggle",
+  "group",
+  "suggest",
+  "list",
+  "get",
+  "export",
+  "import",
+  "set_secret",
+  "reveal",
+  "secret_list",
+  "knowledge",
+  "corpus_register",
+  "corpus_list",
+  "corpus_get",
+  "corpus_route",
+  "corpus_grant",
+  "corpus_deny",
+  "corpus_access",
+  "corpus_consume",
+  "corpus_acquisitions"
+]

addedInput schema / properties / corpus_access_domains

Added value: +{
+  "description": "Knowledge domains granted access (corpus_register).",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

addedInput schema / properties / corpus_access_public

Added value: +{
+  "description": "Whether every entity may consume it (corpus_register; default false).",
+  "type": "boolean"
+}

addedInput schema / properties / corpus_body

Added value: +{
+  "description": "Document reference text (corpus_register).",
+  "type": "string"
+}

addedInput schema / properties / corpus_denies

Added value: +{
+  "description": "Entity ids explicitly denied access (corpus_register).",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

addedInput schema / properties / corpus_document_id

Added value: +{
+  "description": "Corpus document id (corpus_get/corpus_route/corpus_grant/corpus_deny/corpus_consume).",
+  "type": "string"
+}

addedInput schema / properties / corpus_domain

Added value: +{
+  "description": "Knowledge domain (corpus_register/corpus_route/corpus_list).",
+  "type": "string"
+}

addedInput schema / properties / corpus_domains

Added value: +{
+  "description": "Knowledge domains the entity may access (corpus_access).",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

addedInput schema / properties / corpus_entity_id

Added value: +{
+  "description": "Entity acquiring or inspected (corpus_consume/corpus_acquisitions/corpus_access/corpus_grant/corpus_deny).",
+  "type": "string"
+}

addedInput schema / properties / corpus_grants

Added value: +{
+  "description": "Entity ids explicitly granted access (corpus_register).",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

addedInput schema / properties / corpus_mode

Added value: +{
+  "description": "read, research, taught, or import (corpus_consume; default read).",
+  "enum": [
+    "read",
+    "research",
+    "taught",
+    "import"
+  ],
+  "type": "string"
+}

addedInput schema / properties / corpus_source_profile

Added value: +{
+  "description": "Trusted source profile the domain is routed from (corpus_register; default manual).",
+  "type": "string"
+}

addedInput schema / properties / corpus_title

Added value: +{
+  "description": "Document title (corpus_register).",
+  "type": "string"
+}

Addedv1.0.3Sep 29, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Beyond the destructiveHint=true annotation, the description discloses the GM/Editor badge requirement for mutations, that mutations persist to the Novel, the undo path via manage_history (action: undo), that import defaults to a non-mutating dry-run while merge/replace write, and that game_master badge_scope hides entries from the Player badge. It also enumerates the read-only subset (list, get, export, secret_list, knowledge), which matters because the tool's aggregate annotation is destructive. Idempotency is unaddressed but the disclosure burden is otherwise well covered.

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 purpose first, then action families, then behavior, then use/avoid routing — a sensible order for a 14-action mega-tool. It is dense but nearly every clause carries information; the only mild redundancy is restating the read-only action list after already naming them in the action walkthrough.

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 14-parameter, multi-mode tool with an output schema and destructive annotation, the description covers scope, permissions, dry-run defaults, and undo. Gaps are minor: idempotency of set vs. update, and what happens when import merge collides with an existing key.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3, but the description adds real meaning: badge_scope's game_master value hides the entry from the Player badge (a visibility rule not present in the enum description), and it names the recall triggers/priority/sticky weight fields as write-time concepts. It doesn't explain how triggers actually fire or what sticky weight governs.

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 opening sentence names a specific verb and resource ("Manage the active Novel's lore entries — shared, durable world facts") and immediately enumerates the action families it covers. It explicitly names the siblings it is not (manage_belief, manage_corpus), so an agent can separate it from adjacent tools without opening either 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?

The description provides an explicit "Use when:" list and an explicit "Do NOT use when:" clause that routes to named alternatives (manage_belief for entity beliefs, manage_corpus for cold-reference documents). The condition that selects each alternative is stated, not inferred.

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