Skip to main content
Glama
Sign In
Buildup

Buildup

by SNX830
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

add_wheels

Add left and right wheels per axle as separate parts with axle data for XML, including steer and drive flags.

Instructions

Add a left and a right wheel per axle, as separate parts with axle data for the XML.

Wheels are cylinders along X named wheel_fl, wheel_fr, wheel_bl, wheel_br (f = front, b = back, l = left -X, r = right +X; 1 axle: m, 3 axles: f, m, b; 4: f, m1, m2, b). Example for a body 16 voxels wide and 40 long: axles [{z: -13, steer: true}, {z: 13, drive: true}], diameter 8, width 2, inner_x 9 (wheels at X -11..-9 and 9..11). The body must not overlap the wheels: raise the body or carve wheel arches.

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": {
      "project": "<project>",
      "axles": "<axles>",
      "diameter": "<diameter>",
      "width": "<width>",
      "inner_x": "<inner_x>",
      "tire_color": "<tire_color>"
    },
    "name": "add_wheels"
  }
}

Input Schema

NameRequiredDescriptionDefault
axlesYesAxles, any order; usually front [z<0, steer] and back [z>0, drive].
widthYesWheel width along X (voxels).
inner_xYesDistance from X = 0 to the inner face of each wheel: half the body width + 1 leaves a 1-voxel gap outside the body (as on the car verified in game).
projectYesProject name, for example 'red_pickup'.
diameterYesEven number of voxels; the calibration car used 8.
rim_colorNoColor name of the rim (center); default: tire.
tire_colorYesColor name of the tire.
axle_heightNoY of the axles; default diameter / 2 (wheels touch Y = 0).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations declare a non-destructive write (readOnlyHint=false, destructiveHint=false), and the description adds valuable behavior beyond that: it creates multiple named parts (wheel_fl/fr/bl/br) in one call and warns that body geometry must not overlap the result. It does not say whether existing wheels are replaced or how name collisions are handled, which keeps it from a 5.

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?

The core purpose is front-loaded in the first sentence, followed by naming convention, a concrete example, and a placement warning. It is dense and mostly earns its length, though the axle-count naming enumeration is somewhat long for marginal benefit.

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

Completeness4/5

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

With 8 parameters, 6 required, no output schema and no nested objects beyond AxleSpec, the description covers naming, geometry, and the overlap constraint well. It omits what happens on failure/overlap and whether prior wheels are replaced, but nothing essential to invoking it correctly is missing.

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

Parameters4/5

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

Schema description coverage is 100%, so the baseline is 3, but the description adds genuine meaning the schema lacks: the worked example ties axles, diameter, width and inner_x together (inner_x 9, width 2 → wheels at X -11..-9 and 9..11) and explains the naming derivation across 1–4 axles. That is added value above the per-parameter text.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Add a left and a right wheel per axle, as separate parts with axle data for the XML') plus the scope of what it produces. This is clearly a higher-level semantic wheel builder, distinguishable from generic draw_cylinder/draw_box siblings without opening any schema.

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?

The description supplies a prerequisite constraint ('The body must not overlap the wheels: raise the body or carve wheel arches') and geometric conventions, which implicitly tells the agent when this tool applies. However, it never names an alternative (e.g. draw_cylinder for custom wheels) or states when not to use it, so routing guidance is only implied.

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

Deploy Server

Other Tools