Skip to main content
Glama
FullyDefined – AI for SOLIDWORKS

FullyDefined – AI for SOLIDWORKS

chamfer_edges

Adds an angle-distance chamfer to pre-selected edges with a configurable distance, angle, and flip. Rejects distances too large for the edge, so the chamfer stays valid.

Instructions

Add an angle-distance chamfer to the selected edges. Select first with select_edges. A distance too large for the edges is refused.

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": {
      "distance": "<distance>"
    },
    "name": "chamfer_edges"
  }
}

Input Schema

NameRequiredDescriptionDefault
flipNoFor angles other than 45: measure the distance on the other face
unitNomm, cm, m, inch or ft
angleNoAngle of the chamfer, in degrees
distanceYesDistance of the chamfer

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden. It usefully discloses the selection prerequisite and a failure mode (rejection when the distance exceeds edge capacity), which is real value. However, it says nothing about whether the chamfer becomes a persistent model feature, whether it is reversible/editable, or what units are assumed if 'unit' is omitted.

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

Conciseness5/5

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

Three short sentences, front-loaded with the action, followed by the prerequisite and then the failure condition. Every sentence carries distinct information with no redundancy.

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 4-parameter mutation tool with no annotations and no output schema, the description covers purpose, required prior step, and a failure condition adequately; the remaining parameter detail is fully handled by the schema. It stops short of describing the result or the effect on the model tree, which would complete the picture.

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 description coverage is 100%, so distance, angle, unit, and flip are already documented in the schema, making 3 the baseline. The description adds only a constraint on 'distance' (too large is refused) and the phrase 'angle-distance chamfer', which ties angle and distance together conceptually. No added detail on flip or unit behavior.

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: 'Add an angle-distance chamfer to the selected edges.' An agent can immediately tell this creates chamfer geometry on existing edges, and it is distinguishable from fillet_edges by the operation named. It does not explicitly contrast with fillet_edges, keeping it from 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 Guidelines4/5

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

Gives an explicit prerequisite — 'Select first with select_edges' — naming the sibling tool that must run before this one. It also states a precondition for success ('A distance too large for the edges is refused'). It lacks guidance on when to chamfer versus fillet, but the selection workflow is unambiguous.

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

Deploy Server

Other Tools