Skip to main content
Glama

create_finger_joint

Generate finger joints (box joints) between two components in SketchUp for secure and precise woodworking connections. Customize joint depth, width, height, number of fingers, and offsets for accurate 3D modeling.

Instructions

Create a finger joint (box joint) between two components

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
board1_idYes
board2_idYes
depthNo
heightNo
num_fingersNo
offset_xNo
offset_yNo
offset_zNo
widthNo

Implementation Reference

  • The handler function decorated with @mcp.tool(), which registers and implements the 'create_finger_joint' tool. It proxies the call to the SketchUp extension's corresponding tool via JSON-RPC.
    @mcp.tool()
    def create_finger_joint(
        ctx: Context,
        board1_id: str,
        board2_id: str,
        width: float = 1.0,
        height: float = 1.0,
        depth: float = 1.0,
        num_fingers: int = 5,
        offset_x: float = 0.0,
        offset_y: float = 0.0,
        offset_z: float = 0.0
    ) -> str:
        """Create a finger joint (box joint) between two components"""
        try:
            logger.info(f"create_finger_joint called with board1_id={board1_id}, board2_id={board2_id}, width={width}, height={height}, depth={depth}, num_fingers={num_fingers}")
            
            sketchup = get_sketchup_connection()
            
            result = sketchup.send_command(
                method="tools/call",
                params={
                    "name": "create_finger_joint",
                    "arguments": {
                        "board1_id": board1_id,
                        "board2_id": board2_id,
                        "width": width,
                        "height": height,
                        "depth": depth,
                        "num_fingers": num_fingers,
                        "offset_x": offset_x,
                        "offset_y": offset_y,
                        "offset_z": offset_z
                    }
                },
                request_id=ctx.request_id
            )
            
            logger.info(f"create_finger_joint result: {result}")
            return json.dumps(result)
        except Exception as e:
            logger.error(f"Error in create_finger_joint: {str(e)}")
            return f"Error creating finger 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 the tool creates a joint, implying a mutation, but lacks details on permissions, side effects, error conditions, or output format. This is a significant gap for a creation tool with complex parameters.

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, efficient sentence that directly states the tool's purpose without unnecessary words. It is appropriately sized and front-loaded, making it easy to parse quickly.

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 (9 parameters, no annotations, no output schema), the description is inadequate. It lacks parameter explanations, behavioral context, and output details, making it incomplete for effective tool use despite its conciseness.

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?

Schema description coverage is 0%, meaning all 9 parameters are undocumented in the schema. The description adds no information about parameters like board1_id, depth, or num_fingers, failing to compensate for the coverage gap and leaving the agent without semantic understanding.

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 a finger joint') and specifies the resource ('between two components'), which is specific and unambiguous. It distinguishes this from siblings like create_dovetail or create_mortise_tenon by naming a different joint type, though it doesn't explicitly contrast them.

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?

No guidance is provided on when to use this tool versus alternatives like create_dovetail or create_mortise_tenon. The description implies usage for finger joints but doesn't specify scenarios, prerequisites, or exclusions, leaving the agent without contextual direction.

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