Skip to main content
Glama

create_dovetail

Generate precise dovetail joints between two components in Sketchup by configuring angles, depth, width, and tail count for accurate 3D modeling.

Instructions

Create a dovetail joint between two components

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
angleNo
depthNo
heightNo
num_tailsNo
offset_xNo
offset_yNo
offset_zNo
pin_idYes
tail_idYes
widthNo

Implementation Reference

  • The handler function decorated with @mcp.tool() that implements the create_dovetail MCP tool. It connects to SketchUp via socket, forwards the joint creation parameters using JSON-RPC to SketchUp's 'create_dovetail' tool, and returns the result.
    @mcp.tool()
    def create_dovetail(
        ctx: Context,
        tail_id: str,
        pin_id: str,
        width: float = 1.0,
        height: float = 1.0,
        depth: float = 1.0,
        angle: float = 15.0,
        num_tails: int = 3,
        offset_x: float = 0.0,
        offset_y: float = 0.0,
        offset_z: float = 0.0
    ) -> str:
        """Create a dovetail joint between two components"""
        try:
            logger.info(f"create_dovetail called with tail_id={tail_id}, pin_id={pin_id}, width={width}, height={height}, depth={depth}, angle={angle}, num_tails={num_tails}")
            
            sketchup = get_sketchup_connection()
            
            result = sketchup.send_command(
                method="tools/call",
                params={
                    "name": "create_dovetail",
                    "arguments": {
                        "tail_id": tail_id,
                        "pin_id": pin_id,
                        "width": width,
                        "height": height,
                        "depth": depth,
                        "angle": angle,
                        "num_tails": num_tails,
                        "offset_x": offset_x,
                        "offset_y": offset_y,
                        "offset_z": offset_z
                    }
                },
                request_id=ctx.request_id
            )
            
            logger.info(f"create_dovetail result: {result}")
            return json.dumps(result)
        except Exception as e:
            logger.error(f"Error in create_dovetail: {str(e)}")
            return f"Error creating dovetail joint: {str(e)}"
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states 'create' which implies a write/mutation operation, but doesn't specify permissions needed, whether it's destructive, rate limits, or what happens upon creation (e.g., if it modifies existing components). This leaves significant gaps in understanding the tool's behavior and safety.

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, making it highly concise and front-loaded. It directly states the tool's purpose without unnecessary elaboration, earning full marks for efficiency.

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?

Given the complexity (10 parameters, no annotations, no output schema), the description is incomplete. It doesn't cover parameter meanings, behavioral traits, usage context, or output details, leaving the agent with insufficient information to reliably invoke this tool. For a creation tool with many parameters, more context is needed.

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%, meaning none of the 10 parameters have descriptions in the schema. The description adds no information about parameters beyond the tool name, failing to explain what tail_id, pin_id, angle, depth, etc., mean or how they affect the joint creation. This is inadequate given the high parameter count and lack of schema documentation.

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 'create' and the resource 'dovetail joint between two components', making the purpose specific and understandable. However, it doesn't explicitly differentiate from sibling tools like create_finger_joint or create_mortise_tenon, which would require mentioning what makes a dovetail joint distinct.

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_finger_joint or create_mortise_tenon, nor does it mention prerequisites or context for creating joints. It lacks explicit usage instructions or exclusions, leaving the agent to infer based on tool names alone.

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