sketchup-mcp

by nguyenduyhust

Overview Schema Source Related Servers Discussions Admin

Local

create_component

Define the type, position, and dimensions to create a new component in SketchUp, enabling direct 3D model generation.

Instructions

Create a new component in Sketchup

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.1.17Aug 4, 2026

TDQS

C2.4/5.0

Behavior2/5

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

No annotions are provided, so the description carries the full burden of behavioral disclosure. It only says 'create', which implies mutation, but does not disclose default behavior (e.g., creation of a cube), coordinate/unit conventions, what happens to the selection, or side effects on the SketchUp model.

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?

The one-sentence description is direct and front-loaded, with no wasted words. However, the extreme terseness reads as under-specification rather than efficient completeness for a tool with three undocumented parameters and no annotation support.

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?

The description covers only the core purpose. With no annotations, 0% schema coverage, undocumented parameters, and no usage or behavior context, an agent would have to guess how to invoke this tool correctly. The output schema may clarify return values, but it does not compensate for missing input semantics.

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

Parameters1/5

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

The input schema has three parameters but zero description coverage, and the tool description names none of them. An agent cannot determine valid values for 'type', the expected format or units for 'position' and 'dimensions', or the meaning of the defaults beyond what the schema literally states.

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 clearly states the verb and object: 'Create a new component in Sketchup'. It is distinct from delete_component, transform_component, and get_selection at the action level. However, it does not differentiate against the other create_* siblings like create_mortise_tenon or specify what kind of component, so it falls short of a 5.

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 about when to use this tool versus delete_component, transform_component, or the other create_* tools. The description simply restates the action without mentioning alternatives, preconditions, or exclusions.

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

Deploy Server