Skip to main content
Glama
hedless

Onshape MCP Server

by hedless
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

create_extrude

Turn a 2D sketch into a 3D solid by generating an extrude feature with defined depth, direction, and boolean operation.

Instructions

Create an extrude feature from a sketch

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoExtrude nameExtrude
depthYesExtrude depth in inches
elementIdYesPart Studio element ID
documentIdYesDocument ID
workspaceIdYesWorkspace ID
operationTypeNoExtrude operation typeNEW
variableDepthNoOptional variable name for depth
sketchFeatureIdYesID of sketch to extrude
oppositeDirectionNoExtrude away from the sketch plane's default normal direction instead of along it

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.4.0
    • addedInput schema / properties / oppositeDirection
      Added value: +{
+  "default": false,
+  "description": "Extrude away from the sketch plane's default normal direction instead of along it",
+  "type": "boolean"
+}
  2. First observedv0.3.0

TDQS

C2.8/5.0
Behavior2/5

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

With no annotations provided, the description carries full responsibility for behavioral disclosure. It only states 'create an extrude feature' without mentioning side effects, such as modifications to the Part Studio or dependencies on sketch validity. No failure conditions or return values are described.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence, but it is under-specified rather than concise in a helpful way. It does not enumerate key aspects, making it minimally informative while technically short.

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?

Given the tool has 9 parameters, 5 required, and no output schema, the description is incomplete. It does not explain the result of the operation, prerequisites (e.g., that a sketch exists), or how parameters like depth and operationType interact. An agent would need to infer much from the schema alone.

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 coverage is 100%, meaning all parameters have descriptions in the schema. The tool description does not add context beyond 'from a sketch', so it does not compensate for complex parameters like operationType or oppositeDirection. Baseline 3 is appropriate since the schema carries the information.

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 clearly states the tool creates an extrude feature from a sketch, naming the verb and resource. It differentiates from siblings like create_revolve and create_thicken, though it does not explicitly contrast with them.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives like create_revolve or create_thicken. The description does not mention prerequisites (e.g., existing sketch) or when not to use it.

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

Deploy Server

Other Tools