Skip to main content
Glama

PartDesign Chamfer

partdesign_chamfer

Chamfers selected edges of a PartDesign feature with a specified leg size, validating and rolling back on failure to keep the Body valid.

Instructions

PartDesign Chamfer on edges of a feature in a Body. edges accepts e_* tags or 'EdgeN' index strings; size is the chamfer leg in mm (> 0).

Validated and rolled back on failure exactly like partdesign_fillet (issue #283), with the same per_edge / allow_partial opt-ins.

Returns {handle, name, volume (mm^3), edges (the 'EdgeN' names actually chamfered), checks {valid, solids, envelope_ok, envelope_growth_mm, envelope_tol_mm}, mode, partial}; when partial is True, also skipped_edges and a warnings entry. On a failed check the feature is removed, the Body's Tip is restored, and BlendCheckFailed is raised naming the offending edges.

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": {
      "feature": "<feature>",
      "edges": "<edges>"
    },
    "name": "partdesign_chamfer"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoPdChamfer
sizeNo
edgesYes
featureYes
per_edgeNo
workspaceNoRun this call in this named workspace
allow_partialNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.5.7
    • addedInput schema / properties / workspace
      Added value: +{
      +  "default": "",
      +  "description": "Run this call in this named workspace",
      +  "title": "Workspace",
      +  "type": "string"
      +}
  2. First observed

TDQS

A3.9/5.0
Behavior5/5

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

Goes well beyond the thin annotations: it discloses the validate-and-rollback contract, that the feature is removed and the Body Tip restored on failure, that BlendCheckFailed is raised naming offending edges, and that partial mode yields skipped_edges plus warnings. That is exactly the operational context a mutation tool needs.

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-loads the operation and the two key parameter semantics, then moves to the return contract. The sentences are dense but each conveys real information; the cross-reference to issue #283 and to partdesign_fillet is slightly wasteful without adding behavior.

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?

With no output schema, the description correctly documents the return shape and failure mode. The remaining gap is guidance on what `feature` must reference and how to obtain edge tags (resolve_edge / list_edges), which matters for a 7-parameter mutation tool.

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 only 14%, so the description must carry the load and it partially does: edges accepts e_* tags or 'EdgeN' strings, size is the chamfer leg in mm and must be > 0. But the required `feature` parameter and `name` are never explained, and per_edge/allow_partial are only deferred to partdesign_fillet's docs.

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 (chamfer on edges of a feature in a Body) and scopes it to PartDesign features. It references partdesign_fillet only as a behavioral analogue, so it never clarifies how this differs from the sibling chamfer_edges or fillet_edges tools.

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 implied by the PartDesign framing and the mention of per_edge / allow_partial opt-ins, but there is no explicit when-to-use or when-not guidance and no routing to chamfer_edges or partdesign_fillet. An agent must infer the choice from names alone.

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