Skip to main content
Glama
flukeatzerocool

holonovel

by flukeatzerocool
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Command

command

Executes parser commands, resolves spatial intent without state changes, and maps natural-language intents to tool calls.

Instructions

Execute a parser command, resolve a spatial intent, or suggest actions from intent. Use when: a player or narrator takes a physical action (execute), needs the outcome of a movement without mutating state (resolve), or wants intent mapped to tool calls (suggest). Do NOT use when: the GM inspects the model directly — use world or lore.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionNoexecute (parser), resolve (non-mutating intent), or suggest (intent → tool calls). Defaults to execute.
intentNoThe intent to resolve or map (resolve/suggest).
commandNoThe natural-language command (execute).
entity_idNoOptional entity context (suggest).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • addedInput schema / properties / action
      Added value: +{
+  "description": "execute (parser), resolve (non-mutating intent), or suggest (intent → tool calls). Defaults to execute.",
+  "enum": [
+    "execute",
+    "resolve",
+    "suggest"
+  ],
+  "type": "string"
+}
    • changedInput schema / properties / command / description
      Previous value: -"The natural-language command, e.g. 'go north', 'look', 'take torch', 'open door'."New value: +"The natural-language command (execute)."
    • addedInput schema / properties / entity_id
      Added value: +{
+  "description": "Optional entity context (suggest).",
+  "type": "string"
+}
    • addedInput schema / properties / intent
      Added value: +{
+  "description": "The intent to resolve or map (resolve/suggest).",
+  "type": "string"
+}
    • removedInput schema / required
      Removed value: -[
-  "command"
-]
  2. First observedv1.0.0

TDQS

A3.7/5.0
Behavior3/5

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

The description explicitly states that resolve does not mutate state, but it does not clearly disclose whether execute mutates state, persists changes, or has side effects. The readOnlyHint annotation is false, which implies potential mutation, yet the description leaves the exact behavioral impact vague. No error, permission, or rollback behavior is mentioned.

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?

The description is compact and structured into use/no-use sections without excessive verbosity. The action-mode list is dense but not redundant. It could be slightly clearer by separating each mode into its own sentence, but the current format is efficient.

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

Completeness3/5

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

The description provides core usage rules but omits examples, expected output format, and specifics about how suggest maps intents to tool calls. It also does not mention which sibling tools are candidates for suggestion or how resolve returns non-mutating results. Given the tool's central role and lack of an output schema, this gap leaves some operational ambiguity.

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 schema provides a description for every parameter, including the action enum values, and the description adds a useful default for action ('Defaults to execute'). The relationship between action and the other parameters (intent, command, entity_id) is reasonably clear from the schema. With 100% schema coverage, the incremental description value is modest but still helpful.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly names the tool's core purpose—executing parser commands, resolving spatial intents without mutation, and suggesting actions from intent. The three action modes are stated directly, and the 'Do NOT use' clause distinguishes it from world/lore inspection. Minor ambiguity remains around what 'parser command' and 'spatial intent' concretely involve, but the overall purpose is identifiable.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The 'Use when' section maps each action enum value to a concrete scenario, giving an agent clear selection criteria. The 'Do NOT use' clause explicitly routes GM model inspection to world/lore tools. It does not enumerate all sibling-tool alternatives, but the provided guidance covers the main decision points.

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