Skip to main content
Glama
onshape-jamcp

onshape-jamcp

Fillet edges

fillet

Round selected edges with a constant-radius blend to soften sharp corners, then verify results through part properties or a screenshot.

Instructions

Round edges with a constant-radius fillet: a smooth, curved blend between the two faces that meet at each edge. Use it to soften corners and sharp edges; use chamfer instead for a flat, angled bevel. The part must already exist (extrude first) and the edge IDs come from get_body_details. It appends one fillet feature at the end of the feature tree and returns its feature_id, name and health (OK / WARNING / ERROR - a radius 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 changes slightly) or a screenshot. Change the radius later with update_feature (parameter radius), remove it with delete_feature.

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>",
      "radius": "<radius>"
    },
    "name": "fillet"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoFeature name shown in the tree.Fillet
radiusYesFillet radius: a number in the configured unit (mm by default), a string with a unit ('1.5 in') or an expression ('#r'). It must fit the adjacent faces, or Onshape reports ERROR.
edge_idsYesEdge IDs to round, 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 / edge_ids / description
      Previous value: -"Edge IDs from get_body_details to round."New value: +"Edge IDs to round, 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."
    • changedInput schema / properties / radius / 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: +"Fillet radius: a number in the configured unit (mm by default), a string with a unit ('1.5 in') or an expression ('#r'). It must fit the adjacent faces, or Onshape reports ERROR."
  2. First observedv1.1.1

TDQS

A4.7/5.0
Behavior5/5

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

Adds rich behavior beyond annotations: describes appending one feature to the tree, returns feature_id/name/health, explains ERROR semantics when radius is too large (feature still exists), and notes it does not measure the result. Annotations already cover mutation safety profile; description fills in operational details an agent needs.

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?

Front-loaded with purpose, then alternative, prerequisites, behavior, verification, and modification. Every sentence earns its place with no redundancy or filler. Well-structured for an agent to parse.

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?

Given the mutation complexity, annotations (readOnlyHint=false, destructiveHint=false, idempotentHint=false, openWorldHint=true), and output schema, the description covers everything an agent needs: prerequisites, alternative, side effects, return values, error handling, and post-call verification.

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 documents all six parameters in detail. The description repeats a few points (edge IDs from `get_body_details`, radius must fit adjacent faces) but adds no new parameter semantics. Baseline 3 is appropriate when the schema does the heavy lifting.

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?

States a specific verb ('Round edges') and resource ('constant-radius fillet'), explains the geometric result, and directly contrasts with the sibling `chamfer` for a different edge treatment. An agent can distinguish it from other edge-modification tools without opening the 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?

Explicitly names the alternative (`chamfer`) and the condition that selects it. Gives prerequisites (part must exist, extrude first), source of edge IDs (`get_body_details`), and follow-up steps for verification (`get_part_properties`, screenshot) and modification (`update_feature`, `delete_feature`).

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