Skip to main content
Glama
danielproxd2

MCP_CAD

by danielproxd2

chamfer

Bevel edges by specifying distance and angle. Use selectors to target edges like hole rims or machined edges for deburring or assembly lead-ins.

Instructions

Chaflán — bevel one or more edges (distance + angle).

Edge addressing, the selector schema (recommended), failure modes, and the batch-all-identical-edges-in-ONE-call rule are IDENTICAL to fillet — see its description. E.g. chamfer every hole rim at the top face (z≈10): chamfer(selector={"filter": {"geom": "circle", "axis": "z", "at_mm": 10, "tol_mm": 0.5}}, distance_mm=1.0)

Standard autoparts use: bolt-hole entry chamfers (lead-in for assembly), deburred edges on machined parts, parting-line breaks on cast housings. 45° distance-angle is the autoparts default; distance-distance and vertex chamfers are deferred.

Args: edge_midpoints_mm: Optional. Edge addressing by midpoint (line edges; from list_edges() e["midpoint_mm"]). distance_mm: Chamfer leg length (the distance the chamfer extends along the edge's faces). Must be > 0. Typical autoparts values: 0.3-0.5mm for deburr, 1-2mm for bolt-hole lead-ins. angle_deg: Angle from the reference face. Must be in (0, 90). Default 45° (standard for almost all autoparts chamfers). flip: If True, the angle is measured from the OTHER adjacent face. Useful when the default direction goes the wrong way. edge_indices: Optional. Edge addressing by (body, index) — required for closed-loop circular edges (midpoint_mm is None for those).

Returns the resulting Chaflán feature (name, type="chamfer", dims).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
flipNo
selectorNo
angle_degNo
distance_mmNo
edge_circlesNo
edge_indicesNo
edge_midpoints_mmNo
Behavior4/5

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

No annotations provided, so the description carries the burden. It discloses parameter behavior, typical values, and the return type. It mentions the batch-all-identical-edges rule and failure modes are identical to fillet, but doesn't detail side effects or nesting limitations.

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 description is well-structured with a clear opening, followed by detailed parameter explanations and an example. It is slightly verbose but every sentence adds value, and it is front-loaded with the main action.

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?

Given 7 parameters, no output schema, and no annotations, the description covers most critical aspects: typical use cases, parameter constraints, and references to fillet for common patterns. It lacks details on edge_circles and the full selector schema, but overall provides sufficient context for an AI agent.

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?

The description adds meaning beyond the schema for 6 of 7 parameters, explaining distance_mm, angle_deg, flip, edge_midpoints_mm, edge_indices, and selector with typical values and use cases. However, it misses edge_circles entirely, and the selector is only briefly described via reference to fillet.

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 the tool's purpose: 'Chaflán — bevel one or more edges (distance + angle).' It also distinguishes from fillet by referencing it for common details and provides an example use.

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?

The description provides explicit usage context with standard autoparts applications, default angles, and deferred features. It directs users to fillet for the selector schema and failure modes, but doesn't explicitly state when not to use or alternatives beyond fillet.

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/solidworks-mcp'

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