Skip to main content
Glama
mhyrr
by mhyrr

create_finger_joint

Generate precise finger joints (box joints) between two components in Sketchup for woodworking or 3D modeling projects. Define width, height, depth, finger count, and offsets to customize the joint design.

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

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • Handler function for the MCP tool 'create_finger_joint'. It logs the call, connects to SketchUp, sends the tool call via JSON-RPC socket communication with the specified parameters, and returns the result as JSON or an error message.
    @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 this is a creation tool, implying mutation, but doesn't address critical aspects like whether this operation is destructive to existing components, requires specific permissions, has side effects, or how it handles errors. The description is too minimal for a tool with 9 parameters and no annotation coverage.

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 gets straight to the point with no wasted words. It's appropriately front-loaded with the core action and resource, making it easy to parse quickly despite its brevity.

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, creation operation) and complete lack of annotations, the description is insufficient. While an output schema exists (which reduces the need to describe return values), the description doesn't address behavioral aspects, parameter meanings, or usage context that would help an agent understand when and how to invoke this tool effectively.

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 9 parameters have descriptions in the schema. The tool description doesn't mention any parameters, failing to compensate for this gap. It doesn't explain what board1_id/board2_id refer to, what units depth/height/width use, or how offsets affect joint placement, leaving parameters semantically unclear.

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 the resource ('a finger joint (box joint) between two components'), making the purpose immediately understandable. However, it doesn't differentiate this tool from sibling woodworking tools like create_dovetail or create_mortise_tenon, which would require specifying what makes finger joints 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_dovetail or create_mortise_tenon. It also lacks information about prerequisites (e.g., whether components must exist) or typical use cases, leaving the agent to infer usage from context 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/mhyrr/sketchup-mcp'

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