holonovel

Identity Management

manage_identity

Destructive

Stage or bootstrap identity material, accept, reject, or revert facets, and read versioned identity snapshots while retaining displaced values in history.

Instructions

Manage a roster character's durable identity: staged candidates, accepted facets, and the versioned compiled kernel. stage imports or authors identity material; accept replaces a facet, retains the displaced value in an internal history, and bumps the identity version; reject marks a candidate rejected without touching accepted facets; revert restores the most recently displaced facet. bootstrap seeds from a character card; accept's perspective defaults to the candidate's stored perspective. Mutation persists the roster and is audited; list and snapshot are read-only and report current facets only. Use when: staging, accepting, rejecting, reverting, or reading identity material. Do NOT use when: recording what a character knows or believes — use manage_belief; editing narrative personality — use manage_character (action: personality).

Input Schema

Name	Required	Description
`card`	No	Character-card fields to stage (bootstrap).
`facet`	No	Identity facet key, e.g. name or calling (stage).
`value`	No	Identity facet value (stage).
`action`	Yes	stage, accept, reject, revert, list, snapshot, or bootstrap.
`source`	No	Provenance label for the candidate (stage; default manual).
`stability`	No	structural, constitutional, core, or developmental (stage; default core).
`perspective`	No	self, biographical, public_reputation, secret, or unknown (stage/accept; default self).
`candidate_id`	No	Identity candidate id (accept/reject).
`character_id`	Yes	Roster character id.

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.

Changed2 schema fields changedv2026.10.16Oct 25, 2026

changedInput schema / properties / action / description

Previous value: -"stage, accept, reject, list, snapshot, or bootstrap."New value: +"stage, accept, reject, revert, list, snapshot, or bootstrap."

changedInput schema / properties / action / enum

Previous value: -[
-  "stage",
-  "accept",
-  "reject",
-  "list",
-  "snapshot",
-  "bootstrap"
-]New value: +[
+  "stage",
+  "accept",
+  "reject",
+  "revert",
+  "list",
+  "snapshot",
+  "bootstrap"
+]

Addedv1.0.3Sep 29, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Goes well beyond the annotations: it discloses that accept retains the displaced value in internal history and bumps the identity version, that reject leaves accepted facets untouched, that revert restores the most recently displaced facet, that mutation persists the roster and is audited, and that list/snapshot are read-only despite the tool-level readOnlyHint=false. This resolves the annotation ambiguity for a destructive-flagged multi-action 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 resource, then per-action semantics, then the use-when/do-not-use routing; nearly every clause supplies decision-relevant information. It is dense and somewhat run-on, but the only mild redundancy is restating the action list twice.

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?

With 9 parameters, enums, a nested card object, and an output schema that covers return values, the description supplies exactly what the structured fields cannot: per-action behavior, side effects, audit persistence, and sibling routing. Nothing needed to invoke it 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 is 3, but the description adds real value by mapping parameters to actions (stage imports/authors, accept/reject use candidate_id, bootstrap seeds from a card) and by clarifying that accept's perspective defaults to the candidate's stored perspective rather than the schema's stated 'self' default. It does not explain the stability tiers (structural/core/developmental) or what a provenance source label is used for.

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 and resource — managing a roster character's durable identity (staged candidates, accepted facets, versioned kernel) — and enumerates every action in the enum. It also explicitly names the sibling tools it is not, so an agent can separate it from manage_belief and manage_character 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?

Has an explicit 'Use when' clause enumerating staging, accepting, rejecting, reverting, and reading, plus a 'Do NOT use when' clause that names the correct alternatives (manage_belief for knowledge/beliefs, manage_character with action: personality). This is the full when/when-not/alternative pattern.

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