Skip to main content
Glama

create_component

Generate and insert a 3D component in SketchUp by specifying dimensions, position, and type. Integrates with Claude AI via SketchupMCP for precise, prompt-driven modeling tasks.

Instructions

Create a new component in Sketchup

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dimensionsNo
positionNo
typeNocube

Implementation Reference

  • The handler function for the 'create_component' tool. It is registered via the @mcp.tool() decorator. The function proxies the tool call to SketchUp's own 'create_component' tool by sending a JSON-RPC request over a socket connection.
    @mcp.tool()
    def create_component(
        ctx: Context,
        type: str = "cube",
        position: List[float] = None,
        dimensions: List[float] = None
    ) -> str:
        """Create a new component in Sketchup"""
        try:
            logger.info(f"create_component called with type={type}, position={position}, dimensions={dimensions}, request_id={ctx.request_id}")
            
            sketchup = get_sketchup_connection()
            
            params = {
                "name": "create_component",
                "arguments": {
                    "type": type,
                    "position": position or [0,0,0],
                    "dimensions": dimensions or [1,1,1]
                }
            }
            
            logger.info(f"Calling send_command with method='tools/call', params={params}, request_id={ctx.request_id}")
            
            result = sketchup.send_command(
                method="tools/call",
                params=params,
                request_id=ctx.request_id
            )
            
            logger.info(f"create_component result: {result}")
            return json.dumps(result)
        except Exception as e:
            logger.error(f"Error in create_component: {str(e)}")
            return f"Error creating component: {str(e)}"
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states this is a creation operation but doesn't mention permissions needed, whether it's destructive to existing components, what happens on failure, or any rate limits. For a mutation tool with zero annotation coverage, this is inadequate.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, clear sentence with no wasted words. It's appropriately sized and front-loaded with the essential action and resource.

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 creation tool with 3 parameters, 0% schema coverage, no annotations, and no output schema, the description is incomplete. It doesn't explain what the tool returns, how parameters work, or behavioral aspects like error handling. It provides only basic purpose without necessary context.

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%, so the description must compensate for undocumented parameters. It mentions no parameters at all, leaving all three parameters (dimensions, position, type) unexplained. The description adds zero value beyond what the schema provides.

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 action ('Create') and resource ('new component in Sketchup'), making the purpose immediately understandable. However, it doesn't differentiate this tool from sibling tools like 'create_dovetail' or 'create_finger_joint' which also create components, so it doesn't reach the highest score.

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?

The description provides no guidance on when to use this tool versus alternatives like 'create_dovetail' or 'create_mortise_tenon', nor does it mention prerequisites or exclusions. It only states what the tool does, not when to use it.

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

Install Server

Other Tools

Related Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/BearNetwork-BRNKC/SketchUp-MCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server