Skip to main content
Glama

Adventure Management

manage_adventure
Destructive

Generate adventure scaffolds or single encounters, then load and list prepared modules for a tabletop campaign.

Instructions

Generate, load, or list adventure content. generate writes a scaffold to target — novel, codex, or both (default novel when one is active, else codex) — using premise; a !force prefix overrides the generation guard. generate_encounter writes one encounter to the Novel using context. Both persist, appear in the audit log, and the most recent write is undoable via manage_history (action: undo). load and list are read-only, and list accepts an optional genre filter. Use when: the GM wants a new adventure scaffold, a single encounter, or to load a prepared module. Do NOT use when: recording a story beat — use manage_story (action: record).

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

Input Schema

NameRequiredDescriptionDefault
slugNoAdventure module slug (load).
actionYesgenerate, generate_encounter, load, or list.
filterNoOptional genre filter (list).
targetNonovel, codex, or both (generate).
contextNoScene context (generate_encounter).
premiseNoAdventure premise (generate).

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. Addedv1.0.3

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already flag a non-read-only, non-idempotent, destructiveHint=true operation, and the description goes well beyond that: it states that generate and generate_encounter persist and land in the audit log, that the most recent write is undoable via manage_history, and that a '!force' prefix overrides the generation guard. It also cleanly separates the read-only actions (load, list) from the mutating ones, which is exactly the behavioral split an agent needs before invoking a destructive tool.

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 verb set, then per-action routing, then use/don't-use conditions — a logical order with no filler sentences. It is dense (heavy em-dash and parenthetical nesting) which slows parsing slightly, but every clause carries actionable information rather than restating the name.

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?

For a four-action tool with a destructive write path, the description covers mutation vs. read actions, persistence, audit logging, reversibility, the force guard, target defaulting, and the excluded use case. Return values are covered by the existing output schema, so nothing an agent needs in order to call this correctly is missing.

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 the baseline would be 3, but the description adds real meaning the schema does not: the default resolution for target ('novel when one is active, else codex'), the fact that premise drives generate and context drives generate_encounter, that filter is optional and genre-scoped, and that slug applies to load. Only minor gap is no format/syntax guidance for premise or slug values.

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?

Opens with a specific verb set and resource ('Generate, load, or list adventure content') and then breaks the tool down action-by-action: generate writes a scaffold to target, generate_encounter writes one encounter, load and list are reads. It distinguishes itself from siblings by naming manage_story for story beats and manage_history for undo, so an agent can place it 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?

Provides both an explicit 'Use when' clause (new adventure scaffold, single encounter, load a prepared module) and an explicit 'Do NOT use when' exclusion routing story beats to manage_story (action: record). It also names the cross-tool path for reverting a write (manage_history, action: undo), which is an alternative selection, not just context.

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