Skip to main content
Glama
flukeatzerocool

holonovel

by flukeatzerocool
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

NPC

npc

Manage non-player characters in a novel by creating, updating, removing, listing, or retrieving NPC details. Use this tool to introduce, revise, or track characters in your story.

Instructions

Manage non-player characters in the active Novel. Use when: introducing, revising, removing, listing, or reading NPCs. Do NOT use when: managing player characters — use character (action: create/import/sheet).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
mindNoOptional GM-only NPC mind (create/update).
nameNoNPC name (create).
goalsNoOptional goals.
actionYescreate, update, remove, list, or get.
npc_idNoNPC identifier (update/remove/get).
locationNoOptional location.
descriptionNoOptional description.
dispositionNoOptional disposition.
ruleset_referenceNoOptional ruleset stat-block reference (create).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.0.2
    • addedInput schema / properties / mind
      Added value: +{
+  "description": "Optional GM-only NPC mind (create/update).",
+  "properties": {
+    "auto_play": {
+      "description": "When true, the narrator plays this NPC from the directive on initiative.",
+      "type": "boolean"
+    },
+    "directive": {
+      "description": "Narrator-facing directive describing how to play this NPC (GM only).",
+      "type": "string"
+    },
+    "private_journal": {
+      "description": "Private journal entries (GM only).",
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    }
+  },
+  "type": "object"
+}
  2. Added

TDQS

A4.4/5.0
Behavior3/5

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

Annotations indicate readOnlyHint=false and openWorldHint=true, but the description does not add further behavioral details such as side effects of destructive actions (e.g., remove) or any preconditions. The schema's action enum partially covers this, but the description itself offers no extra behavioral context.

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 concise (two sentences) and front-loads the primary purpose, followed by usage guidance. It avoids unnecessary detail while covering the essential information, making it easy to parse quickly.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (9 parameters, nested 'mind' object, no output schema), the description provides sufficient context for when and how to use it. It does not describe return values or detailed behavior per action, but the action enum and parameter descriptions fill most gaps. A short example or note on output could improve completeness, but it is not critically 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?

The parameter descriptions in the schema already provide context (e.g., 'NPC name (create)', 'Optional GM-only NPC mind (create/update)'), and the tool description reinforces the action scope. While the tool description does not elaborate on each parameter individually, the schema coverage is high and the existing descriptions are meaningful, adding value beyond bare names.

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 clearly states the tool manages non-player characters in the active Novel and lists specific actions (introducing, revising, removing, listing, reading). It explicitly distinguishes from the sibling 'character' tool for player characters, making the purpose unambiguous and well-differentiated.

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 explicit 'Use when' and 'Do NOT use when' instructions, directing agents to the 'character' tool for player characters. This gives clear guidance on when to select this tool over alternatives.

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

Deploy Server

Other Tools