Skip to main content
Glama
sketchup-mcp2

sketchup-mcp2

by zinin

create_finger_joint

Create a finger (box) joint between two touching boards in SketchUp by setting finger count, dimensions, and offsets; returns cut results for validation.

Instructions

Create a finger joint (box joint) between two boards.

All dimensions in millimeters; offsets shift the joint from the board face's center. Defaults are sized for ~100 mm boards. The two boards must already touch/overlap along the joint axis.

Returns: JSON {board1: {id, name, type, bbox_mm|null}, board2: {...}, boolean_cuts: {attempted, failed}} — non-zero failed means some cuts did not apply (likely non-manifold geometry); verify via bbox_mm.

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": {
      "board1_id": "<board1_id>",
      "board2_id": "<board2_id>"
    },
    "name": "create_finger_joint"
  }
}

Input Schema

NameRequiredDescriptionDefault
depthNoJoint depth in mm
widthNoJoint width in mm
heightNoJoint height in mm
offset_xNoJoint offset from the board face's center along X, mm
offset_yNoJoint offset from the board face's center along Y, mm
offset_zNoJoint offset from the board face's center along Z, mm
board1_idYesEntity ID from a previous response (integer or its string form)
board2_idYesEntity ID from a previous response (integer or its string form)
num_fingersNoNumber of fingers, 1–50

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.4.0
    • changedInput schema / properties / num_fingers / description
      Previous value: -"Number of fingers"New value: +"Number of fingers, 1–50"
    • addedInput schema / properties / num_fingers / maximum
      Added value: +50
  2. Changed15 schema fields changedv0.3.0
    • addedInput schema / properties / board1_id / anyOf
      Added value: +[
      +  {
      +    "type": "integer"
      +  },
      +  {
      +    "minLength": 1,
      +    "type": "string"
      +  }
      +]
    • addedInput schema / properties / board1_id / description
      Added value: +"Entity ID from a previous response (integer or its string form)"
    • removedInput schema / properties / board1_id / minLength
      Removed value: -1
    • removedInput schema / properties / board1_id / type
      Removed value: -"string"
    • addedInput schema / properties / board2_id / anyOf
      Added value: +[
      +  {
      +    "type": "integer"
      +  },
      +  {
      +    "minLength": 1,
      +    "type": "string"
      +  }
      +]
    • addedInput schema / properties / board2_id / description
      Added value: +"Entity ID from a previous response (integer or its string form)"
    • removedInput schema / properties / board2_id / minLength
      Removed value: -1
    • removedInput schema / properties / board2_id / type
      Removed value: -"string"
    • addedInput schema / properties / depth / description
      Added value: +"Joint depth in mm"
    • addedInput schema / properties / height / description
      Added value: +"Joint height in mm"
    • addedInput schema / properties / num_fingers / description
      Added value: +"Number of fingers"
    • addedInput schema / properties / offset_x / description
      Added value: +"Joint offset from the board face's center along X, mm"
    • addedInput schema / properties / offset_y / description
      Added value: +"Joint offset from the board face's center along Y, mm"
    • addedInput schema / properties / offset_z / description
      Added value: +"Joint offset from the board face's center along Z, mm"
    • addedInput schema / properties / width / description
      Added value: +"Joint width in mm"
  3. First observedv0.0.1

TDQS

A4.3/5.0
Behavior4/5

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

No annotations are provided, so the description carries the full burden and does it well: it declares units, warns that defaults assume ~100 mm boards, states the geometric precondition, and explains the failure mode ('non-zero failed means some cuts did not apply (likely non-manifold geometry)') with a verification path via bbox_mm. It stops short of saying the operation mutates both boards irreversibly or how to recover.

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?

Three short blocks, front-loaded with the action, then units/defaults, then the return contract. Every sentence carries information; only the listed return fields overlap with the output schema.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a nine-parameter mutation tool with no annotations, the description covers units, default sizing, geometry prerequisites, and the failure/verification story — enough to call it correctly. It omits whether the operation is reversible and what happens to board identity on partial failure.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning: it restates the unit convention at the tool level and notes that defaults are sized for ~100 mm boards, which the schema does not convey. The offset-centering semantics are already in the schema, so this is a modest lift over baseline rather than a large one.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource — 'Create a finger joint (box joint) between two boards' — and names the synonym so an agent won't confuse it with the dovetail or mortise-tenon siblings. The two named boards make the operation's scope unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives a concrete precondition: 'The two boards must already touch/overlap along the joint axis', which tells the agent when the call is valid. It doesn't explicitly route to create_dovetail or create_mortise_tenon as alternatives, so selection between joint types is left to inference.

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