Skip to main content
Glama
onshape-jamcp

onshape-jamcp

Update feature parameters

update_feature
Idempotent

Change parameters of existing Onshape features to resize extrudes or fillets without rebuilding. Dependent features rebuild automatically, and multiple features can be updated in one request.

Instructions

Change parameters of existing features (for example make an extrude deeper or a fillet larger) without rebuilding them. Dependent features rebuild automatically. To change several features at once pass updates: two requests in total, however many. An automatically named extrude ('Extrude 8 mm') gets its name refreshed when its depth changes (single-feature form).

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

Input Schema

NameRequiredDescriptionDefault
nameNoOptional new feature name.
updatesNoChange SEVERAL features in ONE Onshape request instead of feature_id + parameters. Names are not changed in this form.
element_idYesElement (tab) ID: the string after /e/ in the Onshape URL. Get it from get_document.
feature_idNoFeature ID (list_features) when changing one feature.
parametersNoMap of parameter ID to new value, e.g. {'depth': 25} for an extrude or {'radius': 2} for a fillet. Numbers are lengths in the configured unit (degrees for angle parameters). Strings may carry units ('1 in') or be expressions ('#width'). Booleans and enum names are set as-is. Use list_features with feature_id to see a feature's parameter IDs.
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. First observedv1.1.1

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare non-readonly, idempotent, non-destructive, open-world behavior, so the bar is lower. The description adds genuinely useful behavioral detail beyond that: dependent features rebuild automatically, and automatically generated extrude names are refreshed only in the single-feature form when depth changes — both non-obvious side effects.

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 core action and example in the first sentence, then layers in the bulk-form and naming caveats. Four sentences with no filler, though the naming-refresh parenthetical is slightly dense and could be tightened.

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 100% schema coverage, full annotations, and an output schema, the description only needs to cover behavior and mode selection, which it does. Remaining gaps (error behavior for invalid parameter IDs, whether unspecified parameters are preserved) are minor for this complexity level.

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

Parameters4/5

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

Schema description coverage is 100%, so the baseline is 3; the description still adds value by contrasting the two call shapes (feature_id + parameters vs. `updates`) and highlighting that the bulk form collapses multiple changes into one request while never renaming features.

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+resource ('Change parameters of existing features') with a concrete example ('make an extrude deeper or a fillet larger'), which clearly separates it from creation siblings like add_feature, extrude, and fillet. The 'without rebuilding them' clause further distinguishes it from delete/recreate workflows.

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?

Explains the core context of use (modifying existing features rather than creating them) and directs the agent to the `updates` form when changing several features, framing it as an efficiency choice ('two requests in total'). It stops short of naming explicit alternatives or exclusions, but the intended situation is unambiguous.

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