Skip to main content
Glama
TheoTown MCP Server

TheoTown MCP Server

by d-init-d

theotown_build_building

Places a building draft at given X/Y coordinates with optional rotation (0–3), letting AI agents construct buildings in TheoTown city layouts.

Instructions

Place a building draft at (x, y) with optional rotation (0-3).

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": {
      "x": "<x>",
      "y": "<y>",
      "building_id": "<building_id>"
    },
    "name": "theotown_build_building"
  }
}

Input Schema

NameRequiredDescriptionDefault
xYes
yYes
rotationNo
building_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.9/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 behavioral burden, and it discloses almost nothing: it does not say whether placement consumes money, whether it can fail and how, whether it is reversible, or what the draft-to-execution lifecycle is. The only behavioral hint is "draft", which is left unexplained rather than defined.

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?

A single front-loaded sentence with no filler; the coordinates and rotation constraint come immediately after the action. It is arguably over-compressed rather than wasteful, so it falls just short of ideal.

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 four-parameter mutation tool with no annotations and 0% schema coverage, far more is needed. An output schema exists so return values need not be explained, but the draft-versus-execute lifecycle, the building_id source, and failure/permission behavior are all missing.

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 0%, but the description does add genuine meaning for two parameters: x/y as placement coordinates and rotation as a 0-3 range, which the bare integer schema does not express. It says nothing about the required building_id, however – notably not that IDs come from something like theotown_get_draft_catalog – leaving a required string parameter undefined.

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 names a specific verb and resource ("Place a building draft") and the coordinates plus rotation it accepts, which distinguishes it from siblings like theotown_build_road and theotown_build_zone by resource type. The one ambiguity is "draft" – it is unclear whether this constructs immediately or only stages a plan for later execution, which matters given siblings such as theotown_execute_plan and theotown_validate_plan.

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 tool versus theotown_build_road, theotown_build_utilities, theotown_build_zone, or the plan-oriented tools. No prerequisites are stated either – nothing about valid terrain, zoning, cost, or whether a draft must subsequently be validated or executed.

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