SketchUp MCP untuk Windows

Overview Schema Source Related Servers Discussions Admin

transform_component

Move, rotate, or scale a SketchUp entity by ID using relative inch offsets and degree rotations to adjust components directly.

Instructions

Move, rotate or scale an entity by ID.

position is a RELATIVE translation in inches (it is added to the current position, it is not an absolute target). rotation is in degrees.

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

Name	Required	Description	Default
`id`	Yes
`scale`	No
`position`	No
`rotation`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.4.0Oct 1, 2026

TDQS

B3.4/5.0

Behavior3/5

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

With no annotations, the description carries full disclosure burden. It usefully reveals that position is a RELATIVE translation added to the current position (not an absolute target) and that rotation is in degrees, which is real behavioral value. However, it omits scale semantics, units for scale, and whether omitted parameters leave the entity unchanged.

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?

Front-loaded with the action, then parameter clarifications in short sentences. The emphasis on RELATIVE is justified because it prevents a costly misuse, though the sentence fragmentation is slightly awkward.

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

Completeness3/5

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

An output schema exists so return values need not be described, and the critical relative-position semantics are covered. Still, for a mutation tool with no annotations and 0% schema coverage, the missing scale semantics and the behavior of unspecified optional parameters leave a real gap.

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

Parameters3/5

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

Schema description coverage is 0%, so the description must compensate. It documents position (relative, inches) and rotation (degrees) but says nothing about scale or the meaning/format of id, leaving two of four parameters unexplained.

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, or scale an entity by ID. This clearly separates it from siblings like create_component, delete_component, and set_material.

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

Usage Guidelines2/5

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

No guidance on when to use this versus alternatives such as create_component or delete_component, and no prerequisites or constraints stated. The agent must infer usage entirely from the verb.

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

Deploy Server