Skip to main content
Glama
SolidWorks MCP Python

SolidWorks MCP Python

by locense

Extend Sketch Entity

sketch_extend

Lengthen a sketch entity from the end nearest a specified point until it reaches the next entity, closing gaps such as lines that stop short of a circle.

Instructions

Lengthen a sketch entity from its end nearest a point until it meets the next entity.

Use it to close a gap, such as lines that stop short of a circle. point ([x, y] sketch mm) is on the entity, near the end to lengthen. Needs: an open sketch with an entity at the point and another in its way. Changes: that end moves to the next entity. Returns: extend with the point and the segment counts. Nothing at the point, or nothing to reach, fails as invalid_input.

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

Input Schema

NameRequiredDescriptionDefault
input_dataYes`point`, `[x, y]` in sketch mm.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare this is a non-read-only, non-destructive, non-idempotent mutation. The description adds useful behavioral context beyond annotations: the selected end moves to the next entity, prerequisites are stated, and failure returns invalid_input. It leaves some details uncovered, such as undo behavior or whether repeated extends are idempotent.

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?

The description is front-loaded with the core operation and then compactly covers usage, point meaning, prerequisites, changes, return value, and error behavior. Every sentence adds practical information without wasted wording.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Even though an output schema exists, the description usefully summarizes the return and failure mode. For a single-parameter mutation tool, it provides enough context about preconditions and effects for an agent to invoke it correctly.

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 schema already describes point as an [x, y] location in sketch mm on the entity near the end to lengthen. The description reinforces this but adds little meaning beyond what the schema already provides, so 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: lengthen a sketch entity from the end nearest a point until it meets the next entity. The purpose is clear and operational, but the description does not explicitly differentiate it from sibling sketch_trim or other editing tools.

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?

Provides a concrete use case, closing a gap such as lines stopping short of a circle, and states prerequisites: an open sketch with an entity at the point and another entity in its way. It also names failure conditions, though it does not explicitly say when to use sketch_trim instead or list exclusions.

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