Skip to main content
Glama
FullyDefined – AI for SOLIDWORKS

FullyDefined – AI for SOLIDWORKS

extrude_sketch

Extrudes the current sketch as a boss, merges it into the touched body, and warns if a separate body results from the wrong direction. A sketch already used by a feature must be redrawn first.

Instructions

Extrude the most recent sketch as a boss (Boss-Extrude). New material merges into the body it touches; the result warns if it made a separate body instead, which usually means the wrong direction. A sketch that already belongs to a feature is not extruded again: draw a new sketch first.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "extrude_sketch"
  }
}

Input Schema

NameRequiredDescriptionDefault
flipNoExtrude in the opposite direction
unitNomm, cm, m, inch or ft
depthNoExtrusion depth (total depth for mid_plane; ignored for through_all / up_to_next)
mergeNoMerge into the existing body (false = keep as a separate body)
end_conditionNoblind = to depth; mid_plane = depth split equally both sides of the sketch; through_all / up_to_next need existing geometry in that directionblind
both_directionsNoLegacy: same as end_condition='mid_plane'

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does real work: it explains the merge-into-touching-body behavior and that a separate-body warning usually signals the wrong direction. It does not cover permission needs or what the success response looks like, but the key failure mode is disclosed.

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?

Three short sentences, no filler, and the core action is front-loaded before the merge caveat and the sketch-reuse restriction. Every sentence adds information an agent would otherwise have to guess.

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 6-parameter, zero-required, no-annotation, no-output-schema tool, the definition covers the pitfalls an agent would most likely hit (consumed sketches, wrong direction producing a separate body). It could say more about what happens with zero arguments or how the result is reported, but nothing critical 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 coverage is 100%, so depth, flip, merge, end_condition and unit are already fully documented. The description adds only indirect meaning — the 'wrong direction' hint maps loosely to flip/direction, and the merge statement restates what the merge parameter documents — so the baseline 3 is appropriate.

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?

States a specific verb and resource ('Extrude the most recent sketch as a boss (Boss-Extrude)') and pins the scope to the most recent sketch. The 'boss' framing and 'new material' wording implicitly separates it from cut_extrude and extrude_surface, though no sibling is named outright.

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 a clear when-not rule ('A sketch that already belongs to a feature is not extruded again: draw a new sketch first') and a directive alternative (draw a new sketch). It lacks explicit guidance on choosing between boss extrude and the sibling cut/surface extrudes, so the routing is implied rather than stated.

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