Skip to main content
Glama
SketchUp MCP

SketchUp MCP

by camilin7483

transform_component

Move, rotate, and scale a SketchUp component by ID or name using x,y,z values for translation, rotation, and scale.

Instructions

Mueve/rota/escala componente. Formato: 'x,y,z' para cada uno.

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_or_name": "<id_or_name>"
    },
    "name": "transform_component"
  }
}

Input Schema

NameRequiredDescriptionDefault
scaleNo1,1,1
rotationNo0,0,0
id_or_nameYes
translationNo0,0,0

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.6/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full burden. It does not disclose the critical behavioral question of whether the transform is absolute (replaces the current transform) or relative (applied as a delta), nor does it mention error behavior for an unknown id_or_name or whether the change is undoable.

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?

It is two short sentences with the core operation front-loaded and no filler, so nothing is wasted. However, the brevity comes at the cost of under-specification rather than being an efficient summary of a well-understood operation.

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

Completeness2/5

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

For a mutation tool with four undocumented parameters, no annotations, and no sibling guidance, this is too thin; an output schema exists so return values need not be explained. The essential missing pieces are relative-vs-absolute transform semantics and rotation units, both of which an agent needs to call this correctly.

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

Parameters2/5

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

Schema description coverage is 0% across four parameters, so the description must compensate and largely does not. The single addition is the 'x,y,z' string format, which is genuinely useful, but it leaves rotation units (degrees vs radians) unspecified, does not explain how id_or_name resolves, and does not clarify the defaults' effect when an argument is omitted.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a concrete resource (component) and three specific verbs (move/rotate/scale), so an agent knows exactly what operation it performs. It does not differentiate itself from siblings like create_component or delete_component, and it is written in Spanish while the tool name and schema are in English, which is a minor inconsistency but not a blocker.

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?

There is no guidance on when to use this tool versus siblings such as create_component, set_material, or get_selected_components, and no mention of prerequisites like first obtaining an id via get_selection. Only a string format hint is provided, which is parameter-level rather than usage-level guidance.

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