holonovel

Set Active Badge

set_badge

Destructive

Switch the active badge to player, game_master, observer, or none to gate tool access for the current Novel, enabling role-based play, spectating, or editing.

Instructions

Switch the active badge to player, game_master, observer, or none (Editor), gating tool access server-side for the active Novel; always callable. The badge is per Novel and switching re-filters tools/list immediately, so a narrower badge can revoke tools mid-task and switching back restores them; badge changes are mutating session state, audited, and reversible by switching back. Use when: entering the story, spectating, or stepping away to edit. Do NOT use when: answering a pending workflow decision — use respond_decision.

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": {
      "badge": "<badge>"
    },
    "name": "set_badge"
  }
}

Input Schema

Name	Required	Description	Default
`badge`	Yes	The badge to activate: player, game_master, observer, or none (Editor).

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.

Changed1 schema field changedv1.0.3Sep 29, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": {},
+  "properties": {
+    "status": {
+      "description": "Machine-readable result status: OK, NEED_INPUT, WARNING, PARTIAL, or an error category (REQ-002, REQ-548c).",
+      "type": "string"
+    },
+    "text": {
+      "description": "Human-readable text envelope mirroring the structured result (REQ-001, REQ-548a).",
+      "type": "string"
+    }
+  },
+  "required": [
+    "status"
+  ],
+  "type": "object"
+}

First observedv1.0.0Sep 2, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Goes well beyond the annotations: discloses that access is gated server-side for the active Novel, that tools/list is re-filtered immediately, that a narrower badge can revoke tools mid-task, and that changes are audited and reversible. This meaningfully expands on destructiveHint=true, which alone would not tell an agent that the 'destruction' is revocable tool-access loss.

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-loads the core action and the value list, then layers usage and exclusion in tight labeled clauses; the density is high but nearly every clause carries operational information, though the single opening sentence is long.

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?

Covers scope, side effects, reversibility, auditability, timing of the tools/list re-filter, and an explicit exclusion; with an output schema present, no return-value explanation is needed. Nothing an agent needs to call it safely is missing.

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% and the enum is fully documented, so the baseline is 3; the description's only added nuance is the per-Novel scoping of the badge, which is about behavior rather than the parameter itself.

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?

States a precise verb+resource ("Switch the active badge") and enumerates the exact target values plus per-Novel scope, so it is unmistakable against siblings like manage_session or respond_decision.

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?

Explicit "Use when: entering the story, spectating, or stepping away to edit" and an explicit exclusion routing pending workflow decisions to respond_decision -- a named alternative with the condition that selects it.

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