nx-ai-bridge

Overview Schema Source Related Servers Discussions Admin

chamfer

Apply symmetric edge offsets in millimetres to modify NX model edges; select edges by ID, nearest point, or all edges of a body. Use list_edges to find edge IDs.

Instructions

Chamfer edges with a symmetric offset. Use list_edges to find edges. Units: millimetres (mm) and degrees.

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"
  }
}

Input Schema

Name	Required	Description
`edges`	No	Edges to modify. Each item is either an edge id from list_edges (e.g. "E:B1:3") or an object {"near": [x, y, z], "body": "B1"?} that picks the edge closest to that point.
`distance`	Yes	Chamfer offset (mm).
`all_edges_of_body`	No	Shortcut: chamfer every edge of this body.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 13, 2026

TDQS

B3.3/5.0

Behavior3/5

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

With no annotations, the description carries the full disclosure burden. It usefully reveals the operation is a symmetric offset and specifies units, but it omits mutation semantics (that this modifies model geometry, whether a history feature is created, reversibility) and any failure behavior. It adds real context but leaves significant behavioral gaps for a write operation.

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?

Three short sentences, front-loaded with the core action and followed by the workflow hint and units. The closing mention of degrees is wasted since no angle parameter exists, but otherwise the text is tight.

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 three-parameter tool with full schema coverage and no output schema, the description covers the main action, how to source edge inputs, and units. What remains missing, namely return value (e.g. a created feature id) and mutation/undo behavior, is modest but still a gap.

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

Parameters2/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds little beyond the schema: it restates the mm unit already present in the distance field and mentions degrees even though no parameter takes an angle, which is misleading rather than clarifying. The description therefore contributes no net semantic value and slightly confuses the unit story.

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 states a specific verb and resource ("Chamfer edges with a symmetric offset"), so an agent immediately knows this creates a chamfer feature. It does not explicitly distinguish itself from the related edge_blend sibling, which is why it falls 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?

It provides one concrete workflow pointer, "Use list_edges to find edges," which tells the agent how to obtain the required edge identifiers. However, it never says when to choose chamfer over edge_blend, nor does it state any prerequisites or exclusions, so guidance is implied rather than explicit.

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