Skip to main content
Glama
zinin

sketchup-mcp2

by zinin

transform_component

Transform a SketchUp component by setting absolute position in mm, relative rotation in degrees, and relative scale factors about its bounding-box center.

Instructions

Move, rotate and/or scale a group or component (mm / degrees).

  • position: ABSOLUTE target for the entity's bounding-box MIN corner, in mm — the same anchor create_component uses. Applied LAST (after rotation/scale), so the final bbox-min lands exactly at [x, y, z] even in combined calls. It is NOT a relative offset: repeating the same position is idempotent.

  • rotation: RELATIVE rotation in degrees around the bbox center, applied sequentially about world X, then Y, then Z.

  • scale: RELATIVE scale factors about the bbox center.

These validations (3-element lists, non-zero scale) apply only to this typed tool — raw Ruby driven through eval_ruby bypasses them.

Returns: JSON {id, name, type, bbox_mm{min,max}|null}. Read bbox_mm to verify the result; it is null for empty geometry.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesEntity ID from a previous response (integer or its string form)
scaleNorelative factors about bbox center, each |s| > 1e-9
positionNoABSOLUTE target for the bbox-min corner, mm
rotationNorelative degrees around bbox center, applied X then Y then Z

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

No annotations provided, so description carries full burden. It discloses position as absolute and applied last, rotation as relative sequential about world axes, scale as relative with non-zero validation, and return JSON structure. All key behavioral traits are explained beyond schema.

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?

Concise bullet-pointed description with no fluff. Each sentence provides essential information about parameters, validations, and output. Front-loaded with main action.

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?

Given the tool has 4 parameters with full schema coverage and an output schema, the description covers all needed context: operation order, validation scope, return format, and verification hint (read bbox_mm). No gaps perceived.

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

Parameters5/5

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

Schema coverage is 100%, but description adds critical semantics: position is NOT relative but absolute and idempotent, rotation order is X then Y then Z, scale factors are relative with non-zero constraint. These enrich the parameter understanding significantly.

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?

Description clearly states verb 'Move, rotate and/or scale' and resource 'a group or component', distinguishing it from creation/deletion/evaluation siblings like create_component, delete_component, and eval_ruby. The title is null but name suffices.

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?

Explicitly contrasts with eval_ruby by noting validations only apply to this typed tool, guiding the agent to use this for safe transformations. However, it does not elaborate on when to prioritize this over other transformation-like operations among siblings.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/zinin/sketchup-mcp2'

If you have feedback or need assistance with the MCP directory API, please join our Discord server