Skip to main content
Glama
ToungaGH

SketchUp MCP for SketchUp Make 2017

by ToungaGH

move_plane

Move every vertex on one axis-aligned plane of a SketchUp Make 2017 group to resize a room or shift a wall, with guards and dry-run previews.

Instructions

Move every vertex lying on one axis-aligned plane of a group, by (to - from). This is the wall-move / room-resize operation. Takes exactly one undo step, aborts without changing anything if any face would end up non-planar, deletes edges the move stranded, and reports before/after counts (faces, edges, open edges, near-coincident vertices) so the result can be checked with audit_geometry. Refuses a move that would shift only some of a face's corners lying on that plane — which tilts the face without splitting it or making it non-planar — or that would change a face from vertical/horizontal. Reaches into nested groups inside the target group. Refuses by default if the vertices would span more than one collection — name them in 'include' or drop them with 'exclude'. Use dry_run:true to see what would change without changing it. All lengths and coordinates are in metres.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
toYesTarget plane coordinate, in metres
axisYesWhich plane orientation to move
fromYesCurrent plane coordinate, in metres
groupYesGroup to edit. Found at any nesting depth: a top-level group with this name wins, otherwise the name must be unique in the model (an ambiguous name is refused, listing the matches).
dry_runNoReport what would change, change nothing (default false)
excludeNoSkip vertices in these collections, e.g. a door frame that happens to sit in the wall plane.
includeNoOnly move vertices in these collections (a group name, or a full path like 'Basement/Garden door - frame'). Also how you acknowledge a deliberate move spanning more than one collection.
x_rangeNoOnly move vertices whose X is within [min, max]
y_rangeNoOnly move vertices whose Y is within [min, max]
z_rangeNoOnly move vertices whose Z is within [min, max]
toleranceNoHow close a vertex must be to 'from' to count as on the plane (default 1.5 mm)
allow_splitsNoPermit the edit even if it splits faces. Off by default: a split means only part of a face moved and the geometry got folded.
allow_distortionNoPermit the edit even if it tilts a face (only some of its on-plane corners move) or changes a face from vertical/horizontal. Off by default.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0+make2017

TDQS

A4.7/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and delivers: single undo step, atomic abort on non-planar outcome, stranded-edge deletion, before/after count reporting, nested-group reach, refusal on partial-corner tilts or vertical/horizontal flips, and a multi-collection refusal with include/exclude as the override. This is unusually complete disclosure of mutation semantics.

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?

Front-loaded with the core verb+resource+formula, then each following sentence conveys a distinct behavioral fact (undo, abort, edge cleanup, reporting, refusals, nesting, collections, dry_run, units). No filler or repetition of structured fields.

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

Completeness5/5

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

For a 13-parameter, annotation-free mutation tool with no output schema, the description covers the safety profile, refusal conditions, preview mode, units, and the return counts an agent needs to verify results. Nothing essential to calling 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 coverage is 100%, so the baseline is 3, but the description adds genuine meaning: it explains that include/exclude are how you acknowledge a deliberate multi-collection move, and that lengths are in metres. It ties the refusal behavior to specific parameters rather than merely restating them.

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 precise verb (move), the exact resource (every vertex on one axis-aligned plane of a group), the transform formula (by to - from), and even names the real-world operation it corresponds to (wall-move / room-resize). This lets an agent distinguish it from sibling move_entity 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?

Gives clear context (wall-move / room-resize), directs the agent to dry_run:true to preview, and routes verification to audit_geometry. It never explicitly names the alternative tool (move_entity) or states when-not to use this, so it falls short of a full 5.

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