Skip to main content
Glama
SolidWorks MCP Python

SolidWorks MCP Python

by locense

Offset Sketch Entities

sketch_offset

Offset sketch entities by a distance in millimeters, outward or inward, to create walls or clearance in an open sketch. Adds the offset entities and returns their IDs, distance, and direction.

Instructions

Offset sketch entities by a distance in mm, outward or inward, e.g. for a wall or a clearance.

Needs: an open sketch (create_sketch). Changes: adds the offset entities. Returns: offset with id, entities, distance and direction (outward or inward).

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": {
      "input_data": "<input_data>"
    },
    "name": "sketch_offset"
  }
}

Input Schema

NameRequiredDescriptionDefault
input_dataYesA mapping: `entities` (ids to offset), `offset_distance` (mm, default 5) and `reverse_direction` (inward; default off).

Output Schema

NameRequiredDescriptionDefault

No arguments

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?

Beyond the annotations (readOnlyHint=false, idempotentHint=false, destructiveHint=false), the description states the prerequisite sketch state and the effect ('adds the offset entities'), which are facts annotations cannot express. It does not elaborate on how repeated calls accumulate entities or on entity-type support, leaving some behavioral gaps that the non-idempotent hint only partly covers.

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 labelled lines (statement, Needs, Changes, Returns) front-load the action and eliminate prose padding. Every sentence carries information the agent needs before calling.

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 an output schema present, the description need not detail return values, and annotations cover the mutation profile; the description supplies the missing precondition and side effect. A small gap remains around which entity types can be offset and whether interactive sketch state matters.

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% and the nested description already documents entities, offset_distance (mm, default 5) and reverse_direction (inward, default off). The description reinforces the mm unit and outward/inward semantics but adds little beyond what the schema already states, so the baseline of 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?

'Offset sketch entities by a distance in mm, outward or inward' names a specific verb, resource, unit and direction, plus a concrete use case ('for a wall or a clearance'). It is unambiguous, though it never names a sibling or alternative, so it stops short of the top band.

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?

'Needs: an open sketch (create_sketch)' gives an explicit precondition and points at the tool that establishes it, and the wall/clearance examples convey the intended use. There are no exclusions or statements about when not to offset versus other sketch operations.

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