Skip to main content
Glama
TheoTown MCP Server

TheoTown MCP Server

by d-init-d

theotown_build_road

Construct a road segment between two coordinate points in TheoTown to design or extend urban layouts, with optional road type and level parameters.

Instructions

Construct a road segment 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_road"
  }
}

Input Schema

NameRequiredDescriptionDefault
x0Yes
x1Yes
y0Yes
y1Yes
levelNo
road_typeNo$road00

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.8/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden and discloses almost nothing. It implies a mutation (creates road tiles) but says nothing about cost deduction, failure modes for invalid or occupied coordinates, whether existing structures block the segment, or reversibility via theotown_demolish.

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 efficient sentence with the verb first and no filler. It is not padded, though it is arguably over-terse for a six-parameter mutation tool.

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?

An output schema exists, so return values need not be described. However, for a six-parameter write operation with no annotations and 0% schema coverage, the definition leaves too much unsaid about cost, failure conditions, and the two optional parameters.

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 description coverage is 0%, so the description must compensate. It does clarify that x0,y0 and x1,y1 are the two endpoints of a segment, which is genuinely useful structure, but the level and road_type parameters (including the "$road00" default string format) are entirely 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 gives a specific verb ("Construct") and resource ("road segment") plus the coordinate form, so an agent knows exactly what is produced. It does not differentiate from siblings like theotown_build_building or theotown_build_zone, leaving that inference to the agent.

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 build a road versus other build tools, no prerequisites (cost, valid terrain, adjacency, whether it must connect to an existing network), and no mention of alternatives such as theotown_validate_plan or theotown_execute_plan.

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