Skip to main content
Glama
sketchup-mcp2

sketchup-mcp2

by zinin

create_dovetail

Creates a dovetail joint between two boards using specified width, height, depth, and flare angle for woodworking joinery in SketchUp.

Instructions

Create a dovetail joint between two boards.

All dimensions in millimeters; angle is in degrees, valid range (0, 60]. 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 {tail: {id, name, type, bbox_mm|null}, pin: {...}, 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": {
      "tail_id": "<tail_id>",
      "pin_id": "<pin_id>"
    },
    "name": "create_dovetail"
  }
}

Input Schema

NameRequiredDescriptionDefault
angleNoDovetail flare angle in degrees, 0 < angle <= 60
depthNoJoint depth in mm
widthNoJoint width in mm
heightNoJoint height in mm
pin_idYesEntity ID from a previous response (integer or its string form)
tail_idYesEntity ID from a previous response (integer or its string form)
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
num_tailsNoNumber of tails, 1–25

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.4.0
    • changedInput schema / properties / num_tails / description
      Previous value: -"Number of tails"New value: +"Number of tails, 1–25"
    • addedInput schema / properties / num_tails / maximum
      Added value: +25
  2. Changed17 schema fields changedv0.3.0
    • addedInput schema / properties / angle / description
      Added value: +"Dovetail flare angle in degrees, 0 < angle <= 60"
    • addedInput schema / properties / angle / maximum
      Added value: +60
    • 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_tails / description
      Added value: +"Number of tails"
    • 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 / pin_id / anyOf
      Added value: +[
      +  {
      +    "type": "integer"
      +  },
      +  {
      +    "minLength": 1,
      +    "type": "string"
      +  }
      +]
    • addedInput schema / properties / pin_id / description
      Added value: +"Entity ID from a previous response (integer or its string form)"
    • removedInput schema / properties / pin_id / minLength
      Removed value: -1
    • removedInput schema / properties / pin_id / type
      Removed value: -"string"
    • addedInput schema / properties / tail_id / anyOf
      Added value: +[
      +  {
      +    "type": "integer"
      +  },
      +  {
      +    "minLength": 1,
      +    "type": "string"
      +  }
      +]
    • addedInput schema / properties / tail_id / description
      Added value: +"Entity ID from a previous response (integer or its string form)"
    • removedInput schema / properties / tail_id / minLength
      Removed value: -1
    • removedInput schema / properties / tail_id / type
      Removed value: -"string"
    • addedInput schema / properties / width / description
      Added value: +"Joint width in mm"
  3. First observedv0.0.1

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses partial-failure semantics (non-zero 'failed' means cuts did not apply, likely non-manifold geometry) and tells the agent to verify via bbox_mm. It omits mutation-side effects such as whether the joint is undoable or modifies the boards in place.

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?

Front-loaded with the verb and resource, then constraints, then a compact return block. The restated angle range (0, 60] duplicates the schema constraint, a minor redundancy; otherwise every sentence earns its place.

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

Completeness5/5

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

For a 10-parameter geometry-creation tool with no annotations, the description covers the units convention, the positional precondition, default sizing assumptions, and failure interpretation of the return payload. An agent has everything needed to call it and to detect a bad result.

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 baseline is 3; the description still adds value by stating that offsets shift the joint from the board face's center and that defaults are sized for ~100 mm boards — context an agent needs to judge whether to override defaults.

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?

States a specific verb and resource — 'Create a dovetail joint between two boards' — which inherently separates it from the sibling joint builders create_finger_joint and create_mortise_tenon. It never explicitly contrasts the joint types, so the differentiation is left implicit.

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' — plus unit and angle-range constraints. It offers no explicit when-not-to-use guidance or routing to the alternative joint tools.

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