Skip to main content
Glama
FullyDefined – AI for SOLIDWORKS

FullyDefined – AI for SOLIDWORKS

extrude_surface

Extrude the most recent sketch into a surface, including open profiles; construction geometry is ignored and each sketch entity creates one face.

Instructions

Extrude the most recent sketch into a surface (Surface-Extrude). The sketch may be an open profile; construction geometry is ignored. Each sketch entity gives one face, so a sketch holding a single fit spline gives a single face. In an assembly the surface's faces are listed by list_component_faces (marked body = surface) and work in add_mate and measure_distance like any face.

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_surface"
  }
}

Input Schema

NameRequiredDescriptionDefault
flipNoExtrude in the opposite direction
unitNoUnit of depth (mm, cm, m, inch or ft)
depthNoDepth (total depth for mid_plane)
end_conditionNoblind = one side of the sketch plane; mid_plane = half the depth on each sideblind

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/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 well: it discloses that open profiles are allowed, that construction geometry is skipped, and the face-per-entity cardinality rule with a fit-spline example. It omits failure behavior (no active sketch), direction/depth defaults, and whether the operation is reversible.

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 verb and resource, and each sentence contributes distinct information (preconditions, face cardinality, assembly interop). The final sentence is dense and could be split, but there is no filler.

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 4-parameter creation tool with no output schema, the description usefully explains the produced geometry (one face per entity, faces addressable by list_component_faces). Missing only error/precondition handling and the fact that depth/unit are optional with sensible defaults.

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 explains flip, unit, depth, and end_condition including the mid_plane depth interpretation. The description adds nothing about these parameters, so the baseline 3 applies.

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 into a surface') and adds the vendor-style name Surface-Extrude. The emphasis on 'into a surface' distinguishes it in spirit from solid extrude siblings, though no sibling is named explicitly.

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 preconditions that gate use: the sketch may be an open profile and construction geometry is ignored. It also clarifies how the result is consumed in assemblies (list_component_faces, add_mate, measure_distance). It stops short of an explicit 'use this instead of extrude_sketch when…' rule.

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