TheoTown MCP Server

Overview Schema Source Related Servers Discussions Admin

theotown_execute_plan

Submits a batch construction plan to the in-game execution queue, enabling staged execution of multiple building, road, zoning, and utility commands.

Instructions

Submit a batch construction plan to the in-game execution queue.

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": {
      "commands": "<commands>"
    },
    "name": "theotown_execute_plan"
  }
}

Input Schema

Name	Required	Description	Default
`commands`	Yes

Output Schema

Name	Required	Description	Default
`error`	No
`job_id`	Yes
`result`	No
`status`	Yes
`progress`	No
`created_at`	Yes
`session_id`	No
`updated_at`	Yes
`total_steps`	No
`failed_steps`	No
`attempted_steps`	No
`completed_steps`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Nov 11, 2026

TDQS

C2.6/5.0

Behavior2/5

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

No annotations are supplied, so the description carries the full burden of behavioral disclosure. The word 'queue' faintly hints at asynchronous execution, but the description never states whether submission requires prior validation, whether jobs return identifiers for theotown_get_job, whether the effects are irreversible, or what happens on partial failure.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The single sentence is front-loaded and free of filler, which is good, but its brevity reflects under-specification rather than economy. There is room to add the missing validation and queue-behavior context without bloat.

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

Completeness2/5

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

For a mutation tool that submits a batch of untyped commands into an execution queue, the description omits essential context: validation prerequisites, job/ID handling, and irreversibility. The presence of an output schema excuses it from explaining return values, but little else is covered.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0% for the single required 'commands' parameter, which is an array of free-form objects with additionalProperties=true. The description only restates that the plan is a 'batch'; it says nothing about the required shape of each command entry, leaving the only parameter effectively undocumented in both schema and prose.

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 uses a specific verb ('Submit') with a clear resource ('batch construction plan') and destination ('in-game execution queue'), so an agent knows this triggers queued construction. It does not distinguish itself from the sibling theotown_validate_plan, which an agent could easily confuse with this tool given both operate on 'plans'.

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

Usage Guidelines2/5

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

There is no guidance on when to use this versus theotown_validate_plan or the individual build_* tools, and no statement about prerequisites. An agent must infer that validation likely precedes execution and that single-build tools are the alternative for one-off construction.

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

Deploy Server