Skip to main content
Glama
sketchup-mcp2

sketchup-mcp2

by zinin

chamfer_edge

Chamfers every feature edge of a SketchUp group or component by a set distance in mm, skipping curved seams and concave edges so you can bevel solid bodies accurately.

Instructions

Chamfer (bevel) every feature edge of a group/component by distance mm.

Seams of curved surfaces — edges where the surface bends by less than 25° (the two face normals differ by under 25°), such as a cylinder's vertical facet edges or every edge of a sphere — are skipped; the rims of curved surfaces are chamfered segment by segment. Concave (inside-corner) edges, such as the base of a post or the inner corner of an L-shaped block, are skipped too: chamfering them would need added material. A body with no feature edges fails with -32602, as does an inside-out body (faces pointing inward): reverse its faces first. A call starts no new cut after 30 s inside SketchUp and then rolls back, changing nothing. Unreliable on non-manifold geometry.

Returns: JSON {id, name, type, bbox_mm|null, edges_chamfered, stats{attempted, succeeded, subtract_failed, skipped_no_match, skipped_seam, skipped_concave, skipped_curved}} — check stats.subtract_failed == 0 (failed cuts) and stats.skipped_no_match == 0 (edges consumed by earlier cuts).

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": {
      "id": "<id>"
    },
    "name": "chamfer_edge"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesEntity ID from a previous response (integer or its string form)
distanceNoChamfer distance in mm

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv0.3.0
    • addedInput schema / properties / distance / description
      Added value: +"Chamfer distance in mm"
    • addedInput schema / properties / id / anyOf
      Added value: +[
      +  {
      +    "type": "integer"
      +  },
      +  {
      +    "minLength": 1,
      +    "type": "string"
      +  }
      +]
    • addedInput schema / properties / id / description
      Added value: +"Entity ID from a previous response (integer or its string form)"
    • removedInput schema / properties / id / minLength
      Removed value: -1
    • removedInput schema / properties / id / type
      Removed value: -"string"
  2. First observedv0.0.1

TDQS

A4/5.0
Behavior5/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 so richly: it discloses the geometric skip rules (seams <25°, concave edges, curved-surface segmentation), the -32602 failure for bodys with no feature edges and inside-out bodies, a 30 s timeout that rolls back with no changes, and unreliability on non-manifold geometry. It also tells the agent exactly which result stats to verify (subtract_failed, skipped_no_match).

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?

The core operation is stated in the first clause, with skip rules, failure modes, timeout, and return shape following in logical order. It is dense but nearly every sentence carries behavioral information; the return-value recap is slightly redundant given the output schema.

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 mutation tool with no annotations, the description covers geometry preconditions, error codes, timeout behavior, reliability caveats, and post-call verification. Even though an output schema exists, the explanation of what stats mean and which to check adds real value.

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

Parameters3/5

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

Schema coverage is 100% and both parameters are documented there, so the baseline is 3. The description reinforces the mm unit and the all-edges scope of the operation but adds no syntax or format detail beyond the schema.

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 opens with a specific verb and resource: 'Chamfer (bevel) every feature edge of a group/component by distance mm.' That is unambiguous about what the tool does and its scope (all feature edges, not selected ones). It does not explicitly name a sibling like fillet_edge to contrast against, so it stops short of a 5.

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

Usage Guidelines3/5

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

Usage is heavily implied through edge-selection rules (seams under 25°, concave edges skipped) and failure conditions, which tells the agent when this tool will and won't work. However, nothing routes the agent between this and fillet_edge or boolean_operation, and there is no explicit 'use this when...' guidance.

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