Skip to main content
Glama
SketchUp MCP

SketchUp MCP

by camilin7483

create_component

Creates geometric components in a SketchUp scene using cube, sphere, cylinder, face, or custom types with configurable position, size, and material.

Instructions

Crea un componente en la escena. Tipos: cube, sphere, cylinder, face, custom. Position/size como 'x,y,z'.

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

Input Schema

NameRequiredDescriptionDefault
nameYes
sizeNo100,100,100
materialNoDefault
positionNo0,0,0
component_typeNocube

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/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 behavioral burden, yet it says nothing about whether the new component becomes selected, whether names must be unique, whether material must already exist, or how failures are reported. It only discloses the accepted type values and coordinate format.

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?

Two short sentences, front-loaded with the action and followed by the value/format details; nothing is wasted. The second sentence is telegraphic ('Position/size como x,y,z'), which is efficient but slightly cryptic.

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, but for a 5-parameter creation tool with zero annotation coverage the description is thin: material semantics, name uniqueness, default behavior, and side effects are all unaddressed.

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% (titles and defaults only), and the description compensates partially: it gives the valid enum-like values for component_type and the 'x,y,z' format for position and size. The 'name' and 'material' parameters remain unexplained, including whether material references an existing material name.

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 ('Crea un componente en la escena') and enumerates the accepted component types, so an agent knows exactly what gets produced. It does not explicitly contrast itself with siblings like transform_component or set_material, which keeps it 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 explicit when-to-use or when-not-to-use guidance and no mention of alternatives; the agent must infer that this is the creation step preceding transform_component or set_material. Only the implicit context 'en la escena' hints at scope.

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