Skip to main content
Glama

Lore Management

manage_lore
Destructive

Create, revise, remove, import, and control a Novel's lore entries so durable facts remain recallable and Player-visible knowledge stays gated.

Instructions

Manage the active Novel's lore entries — durable facts every caller recalls. set upserts a keyed entry, merging supplied fields into an existing key; update requires an existing key and changes only supplied fields; set_secret, reveal, secret_list, and knowledge control Player-visible facts. import defaults to dry-run; merge overwrites colliding keys and keeps entries not in the import; replace clears first. Triggers fire on scene-text match; sticky counts scenes an entry stays active after its last match. visibility gates Player read access (gm_only default, shared, player_discovered). Mutations require GM/Editor, persist to the Novel, and are undoable; reads are read-only. Use when: creating, revising, removing, toggling, grouping, suggesting, listing, exporting, importing, or controlling knowledge. Do NOT use when: recording one entity's beliefs or perceptions — use manage_belief; handling cold-reference documents — use manage_corpus; storing scratch notes — use manage_note.

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_lore"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyNoLore key (set/update/remove/toggle/group/get).
dataNoJSON or Markdown lorebook data (import).
modeNodry-run, merge, or replace (import).
groupNoGroup name, or null to clear (set/update/group).
actionYesset, update, remove, toggle, group, suggest, list, get, export, import, set_secret, reveal, secret_list, or knowledge.
detailNoReturn full lore entries instead of summary entries (list).
formatNoOptional output format (export).
stickyNoOptional sticky weight (set/update).
contentNoLore content (set/update).
priorityNoOptional priority (set/update).
triggersNoOptional recall triggers (set/update).
entity_idNoEntity to reveal to / whose knowledge to read (reveal/knowledge).
visibilityNogm_only (default), shared, or player_discovered — Player read access (set/update; reveal sets player_discovered).
badge_scopeNogame_master or shared (set/update).
world_targetNoOptional world-model target reference (set/set_secret).

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. Changed1 schema field changedv2026.10.18
    • addedInput schema / properties / visibility
      Added value: +{
      +  "description": "gm_only (default), shared, or player_discovered — Player read access (set/update; reveal sets player_discovered).",
      +  "enum": [
      +    "gm_only",
      +    "shared",
      +    "player_discovered"
      +  ],
      +  "type": "string"
      +}
  2. Changed2 schema fields changedv2026.10.15
    • removedInput schema / properties / group / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedInput schema / properties / group / type
      Added value: +[
      +  "string",
      +  "null"
      +]
  3. Changed14 schema fields changedv2026.10.13
    • 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"
      +}
  4. Changed1 schema field changed
    • 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"
      +]
  5. Changed14 schema fields changedv1.0.5
    • 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"
      +}
  6. Addedv1.0.3

TDQS

A4.8/5.0
Behavior5/5

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

Beyond the annotations it discloses authorization requirements ('Mutations require GM/Editor'), persistence scope, undoability of mutations, that reads are read-only, and the destructive semantics of each import mode ('merge overwrites colliding keys and keeps entries not in the import; replace clears first') plus that import defaults to dry-run. That is exactly the beyond-structured-data context the destructiveHint/openWorldHint flags cannot convey.

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?

Purpose and action semantics are front-loaded and every clause carries information, but the body is a long semicolon-chained paragraph covering fourteen actions, which makes it denser to parse than ideal for an agent scanning for one action. It is appropriately sized for a 15-parameter multi-action tool and wastes no sentences on filler.

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

Completeness5/5

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

Given 14 actions, 15 parameters and an output schema (so return values need no explanation here), the description covers action semantics, auth, destructive modes, defaults, and sibling routing — everything an agent needs to call it correctly. No material gap remains.

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 description coverage is 100%, so the baseline is 3; the description earns above that by explaining what the enums actually do — mode's dry-run/merge/replace effects, visibility as the gate on Player read access, triggers firing on scene-text match, and sticky meaning how many scenes an entry remains active after its last match. Several parameters (badge_scope, world_target, format, detail, priority) get no added explanation beyond the schema, which keeps it from a 5.

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 specific resource ('the active Novel's lore entries — durable facts every caller recalls') and then breaks the tool down by action family (set/update, set_secret/reveal/secret_list/knowledge, import modes). It also explicitly marks its boundaries against siblings manage_belief, manage_corpus and manage_note, so an agent can distinguish it without opening any 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 carries an explicit 'Use when:' enumeration (creating, revising, removing, toggling, grouping, suggesting, listing, exporting, importing, controlling knowledge) and an explicit 'Do NOT use when:' section that routes to three named alternatives with their distinguishing conditions. Nothing about when to pick this tool versus a sibling 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.