Skip to main content
Glama
TheoTown MCP Server

TheoTown MCP Server

by d-init-d

theotown_demolish

Demolish buildings, roads, or zones in a rectangular area starting at (x, y), with optional width and height. Use it to clear selected city tiles for redevelopment.

Instructions

Demolish buildings, roads, or zones within a rectangular area starting at (x, y).

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>"
    },
    "name": "theotown_demolish"
  }
}

Input Schema

NameRequiredDescriptionDefault
xYes
yYes
widthNo
heightNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.1/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 only what is destroyed. It says nothing about permanence, refunds/cost, partial-failure behavior, or whether demolition is immediate or queued as a job — all critical for a destructive 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?

A single front-loaded sentence with no filler, and the scope constraints arrive before the mechanics. It is efficient, though the terseness leaves the behavioral gaps above unaddressed.

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?

An output schema exists so return values need not be described, but for a destructive, unannotated 4-parameter mutation tool the description is too thin — no irreversibility, cost, or failure-mode information is present.

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%, and the description does add real meaning: it establishes (x, y) as the origin of a rectangle whose extent comes from width/height, which the bare 'X'/'Y'/'Width'/'Height' titles do not convey. It still omits units (tiles?), coordinate bounds, and what happens if the rectangle exceeds the map.

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 (demolish) plus the exact resource classes affected (buildings, roads, zones) and the spatial scope. It is clearly the inverse of the theotown_build_* siblings, though it never names an alternative explicitly.

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

Usage Guidelines3/5

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

Usage is implied by the destructive verb and the rectangular-area framing, but there is no explicit when-to-use versus when-not guidance, no mention of validate_plan or cancel_job, and no prerequisite or caution statement.

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