Skip to main content
Glama
onshape-jamcp

onshape-jamcp

Revolve sketch

revolve

Turns a sketch profile around an axis to create a solid of revolution or cut a groove. Draw the profile and construction-line axis in one sketch, then set angle and operation.

Instructions

Revolve the closed regions of a sketch around an axis into a solid of revolution (a bottle, a pulley, a washer) or cut a groove with it (operation 'remove'). Draw the profile on one side of the axis and, in the same sketch, the axis as a construction line. The reply says what changed (parts, volume) and lists the created parts.

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

Input Schema

NameRequiredDescriptionDefault
axisNoThe axis to turn about: the ID of an edge or cylindrical face (from get_body_details) or 'sketch:<feature_id>'. Omit it to use the construction line drawn in the SAME sketch (add a `line` shape with construction=true next to the profile); it must be the only construction line there.
nameNoFeature name (default 'Revolve 360 deg').
angleNoAngle in degrees (default 360: a full revolution).
verifyNoMeasure the Part Studio before and after (two extra requests) and report what changed: part count and total volume, plus a warning when nothing changed (Onshape can accept a feature that does nothing). Set false to save requests.
operationNo'new' creates a separate part; 'add' merges into existing parts; 'remove' cuts material away (a groove, a bore); 'intersect' keeps the overlap.new
part_nameNoName for the part an operation 'new' creates, e.g. 'Flanged bushing'. Give one unless the user chose a name.
symmetricNoPartial revolve: half the angle to each side of the sketch.
element_idYesElement (tab) ID: the string after /e/ in the Onshape URL. Get it from get_document.
only_partsNoPart IDs (list_parts) that 'add', 'remove' and 'intersect' should affect instead of every part touched.
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.
sketch_feature_idYesfeature_id returned by create_sketch.
opposite_directionNoTurn the other way.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.1

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare the mutation profile (readOnlyHint=false, destructiveHint=false, idempotentHint=false). The description goes beyond them by disclosing that verification costs two extra requests and that Onshape can silently accept a feature that does nothing, which is real operational context; it also notes the reply reports changed parts and volume.

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-loaded with the action and nomenclature, followed by the setup prerequisite and a note on the reply. Every sentence carries information, though the reply-format sentence overlaps with the existing output schema.

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 13-parameter mutation tool with an output schema and annotations, the description covers purpose, sketch setup, the remove/groove case, and side effects. The remaining parameter details are adequately handled by the 100%-covered schema.

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 every parameter — axis, angle, operation, symmetric, only_parts — is already documented, and the description's axis/construction-line guidance largely restates the 'axis' parameter text. The examples of resulting solids add only marginal intuition beyond the schema, so the baseline applies.

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 and resource ("Revolve the closed regions of a sketch around an axis") plus the outcome (solid of revolution or a cut groove), with concrete examples (bottle, pulley, washer). An agent can distinguish it from extrude or boolean 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 Guidelines4/5

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

Gives concrete setup instructions — draw the profile on one side of the axis and put the axis in the same sketch as a construction line — and clarifies the 'remove' variant for grooving. It stops short of naming an alternative tool (e.g. extrude) or stating when to prefer revolving over other feature-creating siblings.

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