Skip to main content
Glama
TheoTown MCP Server

TheoTown MCP Server

by d-init-d

theotown_build_utilities

Lay underground pipes or power wires between two coordinate points to connect city utilities.

Instructions

Lay underground pipes or power wires between (x0, y0) and (x1, y1).

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": {
      "x0": "<x0>",
      "y0": "<y0>",
      "x1": "<x1>",
      "y1": "<y1>"
    },
    "name": "theotown_build_utilities"
  }
}

Input Schema

NameRequiredDescriptionDefault
x0Yes
x1Yes
y0Yes
y1Yes
utility_typeNopipe

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 burden, yet it says nothing about cost, whether the build executes immediately or becomes a queued job (siblings like theotown_get_job and theotown_cancel_job hint at async jobs), whether it can fail on invalid or occupied tiles, or whether it is reversible. "Underground" is the only behavioral hint — a placement constraint — but it is not elaborated.

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?

A single front-loaded sentence with the action and the parameter roles, and no filler. Nothing in it is wasted or buried.

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 with five parameters, zero schema description coverage, and no annotations, the definition is thin. It omits the utility_type option, cost/failure behavior, and job semantics; only the existence of an output schema excuses it from describing return values.

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%, so the description must compensate; it does explain that (x0, y0) and (x1, y1) are segment endpoints, which is genuine added meaning over bare titles. However, utility_type is never mentioned despite having an enum and a "pipe" default, and coordinate units, ordering, and bounds are left unexplained.

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 states a specific verb ("Lay") and specific resources (underground pipes, power wires) over a coordinate span, so an agent can tell it apart from build_road or build_building. It stops short of explicitly naming those siblings as alternatives.

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 when-to-use guidance, no preconditions, and no mention of alternatives such as building roads or zones first. The only usage information is the implied fact that this is the utility-placement action.

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