SketchUp MCP untuk Windows

Overview Schema Source Related Servers Discussions Admin

create_component

Creates primitive groups (cube, cylinder, sphere, cone) in SketchUp using inch-based position and dimensions for direct 3D modeling.

Instructions

Create a primitive (type: cube, cylinder, sphere, cone) as a group.

position and dimensions are in INCHES (SketchUp's internal unit).
For a cylinder, position is the corner of its bounding box (not the
centre) and dimensions are [diameter, ignored, height].
A cube placed at z=0 extrudes DOWNWARD (z from -height to 0).
For real modelling work prefer eval_ruby.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "create_component"
  }
}

Input Schema

Name	Required	Default
`type`	No	cube
`position`	No
`dimensions`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.4.0Oct 1, 2026

TDQS

A4/5.0

Behavior4/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 genuinely useful, counterintuitive behavior: a cube at z=0 extrudes downward, and cylinder position is the bounding-box corner rather than the centre. It does not address persistence, undo, or what the created group contains beyond the primitive.

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 purpose followed by the non-obvious unit and geometry caveats, then the alternative-tool pointer. Sentences are dense but each earns its place; the parenthetical layout is slightly cramped but readable.

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

Completeness4/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 no explanation, and the description covers the tricky geometry semantics an agent could not infer. The remaining gap is which shape/position combinations are valid or what happens with an omitted position.

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 description coverage is 0%, so the description must compensate, and it largely does: it fixes the unit (inches), enumerates the type values, and defines the dimensions array per shape ([diameter, ignored, height] for cylinders). It leaves sphere/cone dimension ordering and the null-default meaning of position/dimensions unexplained.

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?

States a specific verb and resource — 'Create a primitive (type: cube, cylinder, sphere, cone) as a group' — and enumerates the supported types. It does not directly differentiate itself from the geometry-oriented siblings (transform_component, build_floor_plan), though the eval_ruby mention hints at its niche.

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 routes heavy modelling work away from this tool: 'For real modelling work prefer eval_ruby.' That names the alternative and the condition selecting it. It stops short of saying when this tool IS the right choice versus transform_component or build_floor_plan.

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

Deploy Server