Skip to main content
Glama
FullyDefined – AI for SOLIDWORKS

FullyDefined – AI for SOLIDWORKS

fully_define_sketch

Fully defines an open SOLIDWORKS sketch by adding missing baseline dimensions from the origin and neutral relations, filling in positions without moving geometry after your own dimensions are set.

Instructions

Last resort, after the user's own dimensions: fully define the open sketch of a part, adding the dimensions and relations it still lacks, measured from the origin (baseline dimensions), with neutral relations only (horizontal, vertical, coincident, tangent; never equal, parallel, symmetric or midpoint). Add the user's own sizes first with add_sketch_dimension; this fills in the rest, mostly positions. Nothing moves. Returns the dimensions added (names and values; report them to the user as "added by SolidWorks, not from your spec"), how many relations were added, the sketch status and anything still free (construction geometry, such as fit_spline's helper lines, does not count, except a mirror line). Refused with no sketch open and on an over-defined sketch.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.8/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and does so: it discloses the baseline-from-origin measurement strategy, an explicit whitelist/blacklist of relation types (never equal, parallel, symmetric or midpoint), the guarantee 'Nothing moves', and two refusal conditions (no sketch open, over-defined sketch). It also explains what the return payload contains, including the caveat that construction geometry like fit_spline helpers is excluded except a mirror line.

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?

The core constraint (last resort, after user dimensions) is front-loaded and most clauses carry real information. The final return-value sentence is a long run-on with nested parentheticals that could be split for readability, which keeps it from a 5.

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?

For a zero-parameter, no-output-schema mutation tool, everything an agent needs is present: preconditions, side-effect profile, relation constraints, failure modes, and the shape of the return value with reporting instructions. No significant gap remains.

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 the baseline is 4. The description correctly implies no input is needed beyond the active sketch state, and adds no misleading parameter expectations.

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 and resource ('fully define the open sketch of a part') and immediately qualifies what it adds ('the dimensions and relations it still lacks'). It is clearly distinguished from add_sketch_dimension and add_sketch_relation by naming both and assigning them the user-supplied sizes/relations role.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit sequencing guidance: 'Last resort, after the user's own dimensions' and 'Add the user's own sizes first with add_sketch_dimension; this fills in the rest, mostly positions.' It names the alternative tool and the condition that selects it, so an agent knows both when to use this and when not to.

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