Skip to main content
Glama

Vow Management

manage_vow
Destructive

Track narrative vows, quests, and obligations by setting them, advancing milestones, resolving or forsaking them, and listing commitments; linked countdowns update with difficulty.

Instructions

Track narrative vows, quests, and obligations with milestones. set creates a vow and suggests a linked countdown whose ticks follow the difficulty track (troublesome 12, dangerous 8, formidable 4, extreme 2, epic 1; scope defaults to shared); accept the suggestion in the briefing to create it. milestone increments progress and any linked countdown; resolve and forsake close the vow as fulfilled or abandoned and keep the record. set identifies the vow with name; milestone, resolve, and forsake use vow_name. Mutations require the GM or Editor badge, persist to the Novel, and are undoable via manage_history (action: undo); resolve and forsake are terminal in the forward direction. Use when: setting, advancing, resolving, forsaking, or listing vows. Do NOT use when: starting a clock timer — use manage_countdown (action: set).

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

Input Schema

NameRequiredDescriptionDefault
nameNoVow name (set).
scopeNogame_master, shared, faction, or party (set).
actionYesset, milestone, resolve, forsake, or list.
reasonNoThe reason for abandoning (forsake).
outcomeNoThe resolution outcome (resolve).
partiesNoParties bound by the vow (set).
vow_nameNoVow name (milestone/resolve/forsake).
difficultyNotroublesome, dangerous, formidable, extreme, or epic (set).
descriptionNoVow description (set).
consequencesNoOptional consequences (resolve).

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.9/5.0
Behavior5/5

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

Beyond the annotations, the description discloses required GM or Editor authorization, persistence to the Novel, undo through manage_history, and that resolve/forsake are terminal only in the forward direction. It also explains that set suggests a linked countdown whose ticks depend on difficulty and default scope, which is substantive behavioral context for a mutation tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is dense but front-loaded, beginning with purpose and then covering action behavior, naming conventions, authorization/undo, and use boundaries. Each sentence adds operational information without repeating the schema wholesale.

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?

Despite the tool's 10 parameters and multiple mutation actions, the description covers the important gaps: permissions, persistence, undoability, terminal semantics, linked countdown behavior, and action-specific naming. Since an output schema exists and schema coverage is complete, the description need not explain return values.

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?

With schema coverage at 100%, the schema already documents parameter names and enums, but the description adds meaning by mapping name to set and vow_name to milestone/resolve/forsake. It also adds the difficulty-to-countdown mapping and the shared scope default, though it does not elaborate on parties, outcome, reason, or consequences beyond schema coverage.

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 states a specific resource and operation set: tracking narrative vows, quests, and obligations with milestones, then enumerates set, milestone, resolve, forsake, and list. It also distinguishes itself from manage_countdown by warning not to use it when starting a clock timer, so an agent can route correctly without opening schemas.

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 guidance for setting, advancing, resolving, forsaking, and listing vows, plus an explicit do-not-use case pointing to manage_countdown for clock timers. The action-to-parameter mapping further clarifies when set versus vow_name actions apply.

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