Skip to main content
Glama

add_sketch_chamfer

Adds a 45° equal-distance chamfer to a sketch corner, replacing the vertex where two lines meet with a new inclined line.

Instructions

Chaflán de croquis — corta una esquina del croquis con un chamfer a 45° (distancia igual en ambos lados). Reemplaza el vértice donde dos líneas se encuentran con una tercera línea inclinada.

Uso típico CSWA Tool Block: las esquinas del outline llevan chamfers como "5×45°" (= distance_mm=5). Es más limpio que dibujar la línea inclinada a mano.

[en: Sketch chamfer — cuts a sketch corner with a 45° equal-distance chamfer. Replaces the vertex where two sketch lines meet with a third inclined line. Typical for the CSWA Tool Block outline.]

Args: line1_x_mm, line1_y_mm: A point that lies ON the first line. Typically near the corner — SW picks the closest segment. line2_x_mm, line2_y_mm: A point that lies ON the second line. distance_mm: The chamfer distance from the corner along EACH line. A 45° chamfer with distance_mm=14 means each adjacent line is shortened by 14 mm and the corner is connected by a new line at 45°. z_mm: Z-coordinate of the points (default 0 — front-plane sketches).

Returns the chamfer's metadata.

Requires the sketch to be in EDIT mode (just like add_sketch_dimension). The two selected lines must be ADJACENT (share an endpoint), else SW rejects the chamfer.

Gotcha: in this binding ISketchManager.CreateChamfer is not universally reachable. If it fails, the recommended workaround is to draw the chamfer manually using two create_line calls.

Related: chamfer (3D edge chamfer, not sketch corner).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
z_mmNo
line1_x_mmYes
line1_y_mmYes
line2_x_mmYes
line2_y_mmYes
distance_mmYes
Behavior5/5

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

No annotations, so description carries full burden. It explains lines must be adjacent, sketch must be in edit mode, chamfer is 45° equal-distance, internal API may fail, and returns metadata. Very transparent.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Description is bilingual (Spanish/English), doubling length unnecessarily. Essential info is front-loaded but redundancy reduces conciseness.

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?

No output schema, but description says returns metadata. Covers prerequisites, gotchas, and parameter usage. Adequate for a simple tool, though output details could be richer.

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

Parameters5/5

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

Schema coverage is 0%, so description must explain parameters. It clearly explains each parameter: line1_x_mm, line1_y_mm as a point on first line, line2 similarly, distance_mm as chamfer distance, and z_mm default. Adds significant value beyond schema.

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?

The description clearly states it cuts a sketch corner with a 45° equal-distance chamfer, replacing a vertex with an inclined line. It distinguishes from sibling tools like add_sketch_fillet (rounds corners) and chamfer (3D edge chamfer).

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?

Provides typical usage for CSWA Tool Block, prerequisites (sketch in edit mode, lines adjacent), and a gotcha with workaround. Distinguishes from 3D chamfer. Lacks explicit when-not-to-use but otherwise strong.

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

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/danielproxd2/MCP_CAD'

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