holonovel

Set Active Badge

set_badge

Destructive

Switch the active badge to player, game_master, observer, or none to gate server-side tool access for the session. Use when entering the story, spectating, or stepping away to edit.

Instructions

Switch the active badge to player, game_master, observer, or none (Editor), gating tool access server-side for the session; always callable. Use when: entering the story, spectating, or stepping away to edit. Do NOT use when: answering a pending workflow decision — use respond_decision.

Input Schema

TableJSON Schema

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

Output Schema

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

Behavior4/5

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

Annotations already declare the safety profile (readOnly false, destructive true, idempotent false), so the bar is lower. The description still adds real context beyond them: the badge gates tool access server-side for the session, and the tool is always callable — useful for reasoning about access loss. It stops short of saying explicitly that switching away can revoke currently available tools mid-task, which is the destructive consequence an agent should weigh.

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?

Three tightly packed clauses: what it does, when to use, when not to use. Front-loaded with the action and scope, no filler sentences, every clause earns its place.

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?

An output schema exists, so return values need not be explained. For a single-enum-parameter state-switching tool with full annotation coverage, the description supplies everything needed to select and call it correctly.

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 description coverage is 100% and the enum is fully documented in the schema, so the description adds nothing new when it lists the same four values. Baseline 3 applies when the schema carries the parameter semantics.

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 specific verb+resource (switch the active badge), enumerates the four allowed values, and names the concrete effect: server-side gating of tool access for the session. An agent can distinguish this from every manage_* sibling without opening a 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?

Gives explicit 'Use when' triggers (entering the story, spectating, stepping away to edit) and an explicit 'Do NOT use when' case that names the correct alternative (respond_decision for a pending workflow decision). Routing is unambiguous.

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