Skip to main content
Glama

chamfer_modify_entity

Update an existing entity's properties by ID—such as center, radius, points, closed status, or layer—and re-verify its geometry to fix open contours or clearance collisions.

Instructions

Update an existing entity's properties by ID (center, radius, points, closed, layer) and re-verify geometry. Use this to fix open contours or clearance collisions.

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": {
      "id": "<id>"
    },
    "name": "chamfer_modify_entity"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesTarget entity ID.
layerNo
centerNo
closedNo
pointsNo
radiusNo
snap_gap_mmNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations at all, the description carries the full burden, and it does disclose one real behavioral trait: geometry is re-verified after the update, and the intended outcome is repairing open contours or collisions. However, it never states that this is a destructive in-place mutation, what happens to unspecified properties (the schema forbids additional ones), whether partial updates are allowed, or what a failed re-verification does. Those are meaningful gaps for a write tool with zero annotation coverage.

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?

Two sentences, front-loaded with the mutation and ID, followed by the use case. Every clause carries information an agent needs, and the parenthetical field list is not redundant because the schema leaves those fields undescribed.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a seven-parameter mutation on geometric entities with no annotations and no output schema, the description leaves too much open: the snap tolerance parameter is unaddressed, the behavior of the re-verification step (what it returns, what happens when it fails) is unexplained, and the in-place/reversibility profile is undocumented. It conveys intent but not enough to call the tool confidently.

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 only 14% (just 'id'), so the description has to compensate and does so partially by naming five of the seven parameters, telling the agent which fields are mutable. It adds no semantics for any of them — no units for center/points, no meaning for 'closed', no explanation of the snapping tolerance. 'snap_gap_mm' is not mentioned anywhere, leaving it fully undocumented.

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 gives a specific verb and resource — 'Update an existing entity's properties by ID' — plus an enumerated field list (center, radius, points, closed, layer) and the side effect of re-verifying geometry. An agent can tell this is a mutation of a single existing entity rather than the reporting/linting siblings. It stops short of naming a sibling it must not be confused with (e.g. chamfer_lint, which also relates to verification).

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?

'Use this to fix open contours or clearance collisions' supplies a concrete triggering condition, which is more than an implied use case. There are no exclusions, prerequisites, or alternative tools named, so the agent gets clear context but no guidance on when a different tool is the better choice.

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