Skip to main content
Glama
onshape-jamcp

onshape-jamcp

Chamfer edges

chamfer

Bevels sharp edges with an equal-distance chamfer, cutting the same amount off both faces for lead-ins and bolt or shaft tips. Appends the feature to the tree and returns its ID and health.

Instructions

Bevel edges with an equal-distance chamfer: a flat, angled cut that takes the same distance off both faces at each edge (a 45 degree bevel on a right-angle edge). Use it for lead-in bevels, bolt and shaft tips and to break sharp edges; use fillet instead for a rounded blend. The part must already exist (extrude first) and the edge IDs come from get_body_details. It appends one chamfer feature at the end of the feature tree and returns its feature_id, name and health (OK / WARNING / ERROR - a distance too large for the geometry gives ERROR with a warning, but the feature still exists). It does not measure the result: confirm with get_part_properties (the volume drops) or a screenshot. Change the size later with update_feature (parameter width), remove it with delete_feature. Only equal distances are supported; for a two-distance or distance-and-angle chamfer use add_feature with raw JSON.

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": {
      "document_id": "<document_id>",
      "element_id": "<element_id>",
      "edge_ids": "<edge_ids>",
      "distance": "<distance>"
    },
    "name": "chamfer"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoFeature name shown in the tree.Chamfer
distanceYesHow far the bevel reaches from the edge along BOTH faces: a number in the configured unit (mm by default), a string with a unit ('0.5 in') or an expression ('#c'). It must fit the adjacent faces, or Onshape reports ERROR.
edge_idsYesEdge IDs to bevel, from get_body_details (include_edges is on by default). IDs can change when the part is rebuilt, so read them again after other edits.
element_idYesElement (tab) ID: the string after /e/ in the Onshape URL. Get it from get_document.
document_idYesOnshape document ID: the 24-character hex string after /documents/ in the document URL. Get it from list_documents.
workspace_idNoWorkspace ID (the string after /w/ in the URL). Optional - defaults to the document's main workspace.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / distance / description
      Previous value: -"Length: a number in the configured unit (see get_settings; mm by default), a string with a unit such as '2.5 in', or an Onshape expression such as '#width'."New value: +"How far the bevel reaches from the edge along BOTH faces: a number in the configured unit (mm by default), a string with a unit ('0.5 in') or an expression ('#c'). It must fit the adjacent faces, or Onshape reports ERROR."
    • changedInput schema / properties / edge_ids / description
      Previous value: -"Edge IDs from get_body_details to bevel."New value: +"Edge IDs to bevel, from get_body_details (include_edges is on by default). IDs can change when the part is rebuilt, so read them again after other edits."
    • addedInput schema / properties / name / description
      Added value: +"Feature name shown in the tree."
  2. First observedv1.1.1

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the annotations it discloses what the call actually does: appends exactly one `chamfer` feature at the end of the tree, returns feature_id, name and health, and that an oversized distance yields ERROR with a warning yet still creates the feature. It also states the tool does not verify the result and points to `get_part_properties` or a screenshot for confirmation, plus the follow-up paths via `update_feature` (parameter `width`) and `delete_feature`.

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 geometry and the sibling exclusion are front-loaded, and the sentences progress logically from what it does, to when to use it, to prerequisites, to outcomes and follow-ups. It is dense but each sentence carries information; slightly long for a single tool but not padded.

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

Completeness5/5

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

For a feature-tree mutation with an output schema, the description covers the gaps that matter: prerequisites, edge-ID sourcing, the appended-feature side effect, health semantics for failures, and how to verify or undo. Nothing an agent needs in order to invoke it correctly is missing.

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 the schema already explains distance, edge_ids, document_id, element_id and workspace_id in comparable detail. The description adds only marginal semantic content: that only equal distances are supported and that the later-editable parameter is named `width`. Baseline 3 is appropriate when the schema carries the parameter burden.

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 opens with a specific verb and geometric operation: 'Bevel edges with an equal-distance chamfer: a flat, angled cut that takes the same distance off both faces.' It explicitly distinguishes itself from `fillet` (rounded blend) and from `add_feature` (two-distance or distance-and-angle chamfers), so an agent can separate it from siblings without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

It names concrete use cases (lead-in bevels, bolt and shaft tips, breaking sharp edges) and explicit exclusions (use `fillet` for rounded, `add_feature` for unequal distances). Prerequisites are spelled out too: the part must already exist via `extrude`, and edge IDs come from `get_body_details`.

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