Skip to main content
Glama
sketchup-mcp2

sketchup-mcp2

by zinin

transform_component

Move, rotate, or scale a SketchUp group or component by ID, setting absolute bbox-min position in mm and relative rotation/scale around its center.

Instructions

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

Groups and component instances only; other entities fail with -32602.

  • 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.

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": {
      "id": "<id>"
    },
    "name": "transform_component"
  }
}

Input 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

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changedv0.3.0
    • addedInput schema / properties / id / anyOf
      Added value: +[
      +  {
      +    "type": "integer"
      +  },
      +  {
      +    "minLength": 1,
      +    "type": "string"
      +  }
      +]
    • addedInput schema / properties / id / description
      Added value: +"Entity ID from a previous response (integer or its string form)"
    • removedInput schema / properties / id / minLength
      Removed value: -1
    • removedInput schema / properties / id / type
      Removed value: -"string"
    • addedInput schema / properties / position / description
      Added value: +"ABSOLUTE target for the bbox-min corner, mm"
    • addedInput schema / properties / rotation / description
      Added value: +"relative degrees around bbox center, applied X then Y then Z"
    • addedInput schema / properties / scale / description
      Added value: +"relative factors about bbox center, each |s| > 1e-9"
  2. First observedv0.0.1

TDQS

A4.8/5.0
Behavior5/5

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

No annotations exist, so the description carries the full burden and does so: it discloses application order (position applied LAST, after rotation/scale), rotation axis order, relative-vs-absolute distinction, idempotency of repeated position, the -32602 failure mode, validation scope versus eval_ruby, and the return payload including bbox_mm being null for empty geometry.

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 one-line summary, then per-parameter bullets, then return contract — no wasted sentences despite the length. The repetition about position not being a relative offset earns its place because it prevents the most likely misuse.

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?

Complete for a 4-parameter mutation tool with no annotations: semantics, ordering, failure mode, validation scope, and the verification signal (read bbox_mm) are all present. The output schema exists, and the description's brief return note is appropriately light.

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 the description goes well beyond it: it explains that position is an absolute bbox-min target rather than a relative offset, that it is applied after rotation/scale so bbox-min lands exactly at [x,y,z] in combined calls, and that rotation/scale are relative about the bbox center. Those composition semantics are not derivable from the schema alone.

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 set and resource (move/rotate/scale a group or component) with units (mm / degrees), and explicitly scopes the entity types it accepts versus the -32602 failure case. An agent can distinguish it from create_component, delete_component, and eval_ruby 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?

Explicitly names the entity restriction ('Groups and component instances only; other entities fail with -32602') and clarifies the relationship to create_component's anchor and to raw eval_ruby, which bypasses these validations. It does not explicitly state when to prefer eval_ruby or a different transform route, so it stops short of full alternative routing.

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