Skip to main content
Glama
FullyDefined – AI for SOLIDWORKS

FullyDefined – AI for SOLIDWORKS

edit_sketch

Reopen an existing SOLIDWORKS sketch for editing so draw tools, relations, and dimensions can modify it; close it to rebuild dependent features. Refused while another sketch is open.

Instructions

Reopen an existing sketch (for example 'Sketch1') for editing. The draw tools, add_sketch_relation and add_sketch_dimension then act on it, and close_sketch rebuilds the features made from it. Refused while another sketch is open.

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": {
      "sketch": "<sketch>"
    },
    "name": "edit_sketch"
  }
}

Input Schema

NameRequiredDescriptionDefault
sketchYesName of the sketch in the feature tree, e.g. 'Sketch1'

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations provided, the description carries the behavioral burden and discloses meaningful traits: the tool is refused while another sketch is open, and close_sketch subsequently rebuilds features from the sketch. It does not cover return values or authentication/permission needs, but the state-dependent refusal and lifecycle context are valuable.

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 sentences, front-loaded with the core action, followed by workflow context and the refusal condition. Every sentence provides useful information without redundancy.

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-parameter tool with no output schema and no annotations, the description covers the essential context: what it does, what depends on it, and when it is refused. Additional detail on failure behavior for nonexistent sketch names would make it complete, but nothing critical is missing for correct invocation.

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 sole 'sketch' parameter is already documented with an example in the schema. The description repeats that example ('Sketch1') but adds no further meaning, such as accepted naming formats or behavior when the name does not exist. Baseline 3 is appropriate.

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?

The description states a specific verb and resource: 'Reopen an existing sketch ... for editing.' It clearly scopes the tool to existing sketches, distinguishing it implicitly from creation tools like create_sketch, and names the related tools that act on the reopened sketch.

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?

It explains when to use the tool (to reopen an existing sketch for editing), describes the downstream workflow with add_sketch_relation, add_sketch_dimension, and close_sketch, and states a precondition ('Refused while another sketch is open'). It stops short of explicitly naming an alternative for creating new sketches, but the usage context is strong.

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