Skip to main content
Glama
FullyDefined – AI for SOLIDWORKS

FullyDefined – AI for SOLIDWORKS

close_sketch

Closes the active sketch, rebuilds features built from it, and converts free sketch sizes into dimensions so the sketch is fully defined before extrusion.

Instructions

Exit the open sketch, rebuilding the features made from it. Call it before an extrude if the sketch has not been closed yet. In a part, the drawn sizes of rectangles, circles, arcs and polygons become dimensions where still free (listed in the result), and anything still free is named by id: dimension it from the references the user named before the feature, which refuses a sketch that is not fully defined.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations at all, the description carries the full burden and does disclose meaningful behavior: features are rebuilt, free sketch entities get auto-created dimensions listed in the result, and the operation refuses a sketch that is not fully defined. What it leaves unclear is whether reopening is possible and what exactly 'rebuilding' costs, but the refusal condition and side effects are covered.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The opening sentence is well front-loaded, but the final clause is a run-on that compresses two ideas (auto-dimensioning free geometry and dimensioning by id from prior references) into an ambiguous sentence with an awkward colon. Meaning is recoverable but the agent has to re-read it.

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 no output schema and no annotations, the description does the right work: it explains the regeneration side effect, notes that created dimensions appear in the result, and states the fully-defined refusal. Only the ambiguous id-dimensioning clause and the absence of any error/recovery detail keep it short of complete.

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?

The tool takes zero parameters, so there is no schema surface to compensate for; baseline 4 applies. The description's references to 'references the user named before the feature' describe preconditions on model state rather than inputs.

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?

The description states a concrete verb and resource: 'Exit the open sketch, rebuilding the features made from it', which tells an agent this finalizes a sketch and regenerates dependent features. It is distinct from siblings like close_document or edit_sketch, though it never explicitly contrasts itself with them.

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 gives a clear precondition-and-action rule: 'Call it before an extrude if the sketch has not been closed yet', which is actionable ordering guidance. It also implies a constraint (the sketch must be fully defined or the call is refused), but it does not name which sibling to use instead if the sketch is still free.

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