Skip to main content
Glama
SolidWorks MCP Python

SolidWorks MCP Python

by locense

Convert Entities

sketch_convert_entities

Copies model edges or a face outline into an open sketch so you can build geometry from existing boundaries instead of redrawing at guessed coordinates.

Instructions

Copy model edges, or a face's whole outline, into the open sketch (Convert Entities).

Use it to sketch on an existing edge exactly, e.g. to cut a pocket that follows a face, instead of re-drawing it at guessed coordinates. Pick edges or a face with a point on each (mm). Needs: an open sketch (create_sketch) and a part with those edges. Changes: adds the copied entities, tied to the edges. Returns: converted with entities (ids for the other sketch tools), count and construction.

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

Input Schema

NameRequiredDescriptionDefault
input_dataYesThe edges. Give `edge_points`, `face_point`, or both; `construction` makes the copies construction geometry.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare this is a write (readOnlyHint=false) that is non-idempotent and non-destructive. The description adds genuinely new behavior: the copied entities are tied to the source edges (a persistent parametric relationship), and it outlines inputs and the returned `converted` payload. It doesn't warn that repeated calls would produce duplicate copies, which the non-idempotent hint implies.

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-loads the action in the first clause, then moves through use case, prerequisites, effects and returns in a predictable order with no filler. Some sentences are wrapped awkwardly mid-phrase ("e.g. to cut a pocket that\nfollows a face"), but nothing is expendable.

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?

Covers everything an agent needs for a nested-parameter mutation: when to use, prerequisites (open sketch, model edges present), what changes (entities added and associated), and what comes back (entity ids usable by other sketch tools). An output schema exists, so the return-value sentence is a bonus rather than a gap-filler.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning: pick edges or a face "with a point on each (mm)", clarifying that coordinates are on-geometry points in millimetres and that edge_points/face_point may be combined. The `construction` flag is left to the schema, which already covers it.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a concrete verb and resource — copy model edges or a face's whole outline into the open sketch — and ties it to the named CAD operation (Convert Entities). This is clearly distinguishable from sibling sketch operations such as sketch_offset or sketch_trim, so an agent can select it without opening the schema.

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 an explicit use case ("sketch on an existing edge exactly, e.g. to cut a pocket that follows a face, instead of re-drawing it at guessed coordinates") plus hard prerequisites: an open sketch from `create_sketch` and a part containing those edges. It stops short of naming an alternative tool or stating when-not to use it, which keeps this from a 5.

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