Skip to main content
Glama
Sign In
3D New Era AI

3D New Era AI

by leandrodaf
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Hybrid

Fill a wall with cabinets

cabinet_run
Destructive

Fill a wall with cabinets sized to fit: measure free stretches between obstacles, split into even modules, and place sinks, cooktops, and drawer units.

Instructions

Fill a wall with cabinets sized for it: measures the free stretches between corners, doors, windows, fridge and stove, splits each into even modules (30-90 cm, no useless leftovers; 15-30 cm pull-outs, fillers under 15; the defaults target=60 max=90 sink_w=80 cooktop_w=60 are the nominal widths of EN 1116, which is what appliances and hardware are made for — bespoke widths in between are fine for a run that receives none), drawer unit beside the stove, countertop on base rows, cabinet over the fridge and hood gap on wall rows, wardrobes (hanging rails, shelves, drawers) on tall rows facing bedrooms; p.sink/p.cooktop place those cabinets and cutouts. Replaces the cabinets already there (keep ids stay). Reply {modules:[[id,role,from,w]],removed,notes}; dry plans only. Change one module afterwards with joinery id.

Input Schema

NameRequiredDescriptionDefault
pNoFlat choices, all optional: row base|wall|tall, h, d, elev, t (mm), front, color and `handle_color` [r,g,b] or "#hex", handle bar|profile|knob|cava|none (bar), drawers (drawer units), max (widest module, 90), target (60), top (base countertop, true), `top_material`, sink / cooktop (center cm along the wall: its cabinet and cutout; null removes it), `sink_w` (80), `cooktop_w` (60), interior shelves|hanging|wardrobe (tall rows; wardrobe by default facing a bedroom)
toNoWhere the run ends, cm from the wall start (default: the wall's end)
dryNoPlan and report only
fromNoStretch to fill, cm from the wall start (default: all of it)
keepNoCabinets on that wall that stay as they are
nearNoOr a piece against the wall (`f12`, the fridge): its nearest wall, on its side
roomNoRoom the fronts face, by id or name (default: toward the house middle)
wallNoWall whose face gets the cabinets

Output Schema

NameRequiredDescriptionDefault
rowYes
wallYes
notesYes
modulesYes
removedYes
adjustedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv3.2.0
    • changedInput schema / properties / p / description
      Previous value: -"Flat choices, all optional: row base|wall|tall, h, d, elev, t (mm), front, color [r,g,b], handle bar|profile|knob|cava|none (bar), `handle_color` [r,g,b] or \"#hex\", drawers (drawer units), max (widest module, 90), target (60), top (base countertop, true), `top_material`, sink / cooktop (center cm along the wall: cabinet under it and the countertop cutout), `sink_w` (80), `cooktop_w` (60), interior shelves|hanging|wardrobe (tall rows; wardrobe by default facing a bedroom)"New value: +"Flat choices, all optional: row base|wall|tall, h, d, elev, t (mm), front, color and `handle_color` [r,g,b] or \"#hex\", handle bar|profile|knob|cava|none (bar), drawers (drawer units), max (widest module, 90), target (60), top (base countertop, true), `top_material`, sink / cooktop (center cm along the wall: its cabinet and cutout; null removes it), `sink_w` (80), `cooktop_w` (60), interior shelves|hanging|wardrobe (tall rows; wardrobe by default facing a bedroom)"
    • changedInput schema / properties / room / description
      Previous value: -"Room the fronts face (default: the side toward the middle of the house)"New value: +"Room the fronts face, by id or name (default: toward the house middle)"
  2. Changed7 schema fields changedv3.0.0
    • removedInput schema / properties / dry / default
      Removed value: -false
    • removedOutput schema / properties / adjusted / description
      Removed value: -"Neighbouring runs replanned, same shape"
    • removedOutput schema / properties / modules / description
      Removed value: -"[id, role, from cm, w cm]"
    • removedOutput schema / properties / notes / description
      Removed value: -"What the rules say about it"
    • removedOutput schema / properties / removed / description
      Removed value: -"Cabinets it replaced"
    • removedOutput schema / properties / row / description
      Removed value: -"base, wall or tall"
    • removedOutput schema / properties / wall / description
      Removed value: -"The wall the run is on"
  3. First observedv0.1.0

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false; the description adds useful specifics beyond that, including 'Replaces the cabinets already there (keep ids stay)', the default module sizes, and the fact that the reply is a plan shape. This gives an agent concrete expectations about mutation and output.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose is front-loaded, but the description is a dense run-on sentence with many semicolon-separated clauses. Every clause carries information, yet the structure makes it harder to scan than necessary for an agent.

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?

Given the complex behavior and the presence of an output schema, the description covers the destructive replacement behavior, module sizing rules, defaults, and the reply shape. It leaves some ambiguity around 'dry plans only' and interaction between overlapping parameters, but it is largely complete for correct invocation.

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 meaningful context for key parameters: defaults such as target=60, max=90, sink_w=80, cooktop_w=60, and the role of p.sink/p.cooktop in placing cabinets and cutouts. It does not explain every parameter, but it enriches the most consequential ones.

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?

The description opens with a specific verb and resource: 'Fill a wall with cabinets sized for it'. It explains the concrete operation—measuring free stretches and splitting them into modules—so an agent can distinguish it from generic layout or joinery tools without opening the schema.

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

Usage Guidelines4/5

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

It states that the tool replaces existing cabinets and that a single module should be changed afterwards with 'joinery id', which gives a clear alternative for follow-up edits. It does not explicitly say when not to use this tool versus siblings such as layout or arrange, so the guidance is strong but not exhaustive.

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