Skip to main content
Glama
Sign In
SolidworksMCP-python

SolidworksMCP-python

by andrewbartels1
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Check Sketch Fully Defined

check_sketch_fully_defined
Read-onlyIdempotent

Check whether a SolidWorks sketch is fully defined, under-defined, or over-defined after adding relations and dimensions to confirm no free geometry remains.

Instructions

Check whether a sketch is fully defined, under-defined or over-defined.

Use it after adding relations and dimensions, to see if the sketch still has free geometry. Needs: an open part with the sketch. Read-only. Returns: sketch with sketch_name, is_fully_defined (null when unknown), definition_state and where the answer came from (source).

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": "check_sketch_fully_defined"
  }
}

Input Schema

NameRequiredDescriptionDefault
input_dataNoNothing is required: give `sketch_name`, or omit it for the open or last sketch.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.0.0
    • changedInput schema / properties / input_data / description
      Previous value: -"Optional sketch selector."New value: +"Nothing is required: give `sketch_name`, or omit it for the\nopen or last sketch."
  2. First observedv1.0.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent and non-destructive, and the description reinforces that plus adds the operational prerequisite of an open part containing the sketch. It also discloses the 'null when unknown' caveat and the `source` field, which the annotations do not cover. It does not explain what happens if the named sketch does not exist, leaving a small gap.

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?

Front-loads the purpose in one sentence, then a usage line, a prerequisite line, and a compact return-value line. Every sentence carries distinct information and 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 single-optional-parameter read tool with an output schema, the description supplies purpose, timing, prerequisite and the meaning of the tricky `null` case. Minor gap: nothing about behavior on an invalid or missing sketch name, though read-only status makes the risk low.

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 documents the default behavior when sketch_name is omitted, so the description largely restates it ('give `sketch_name`, or omit it for the open or last sketch'). It adds no new format or constraint detail, which is acceptable given the schema does the work but warrants only the baseline.

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 specific verb ('Check') and a precise, enumerated outcome space: fully defined, under-defined, over-defined. The resource (sketch definition state) is unmistakable and does not overlap with the check_* siblings, which target drawings and interference.

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 concrete trigger ('after adding relations and dimensions, to see if the sketch still has free geometry') and a prerequisite ('an open part with the sketch'). It does not name an alternative tool or state when not to use it, which keeps it below 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