Skip to main content
Glama
FullyDefined – AI for SOLIDWORKS

FullyDefined – AI for SOLIDWORKS

draw_slot

Adds a straight slot to an open SOLIDWORKS sketch using centre coordinates, centre distance, width and angle, with construction geometry and returned entity IDs.

Instructions

Add a straight slot to the open sketch: two half circles joined by two lines, around a construction centreline. x, y is the slot's centre, centre_distance the distance between the two arc centres, width the slot's width (twice the end radius), angle its direction from +X (0 = horizontal, the default; the result says so). At 0 or 90 degrees it is horizontal or vertical by a relation; centred on the origin it is tied there. In a part its centre distance and end radius (width / 2) become dimensions when the sketch is closed, unless set first: a slot on the origin is then fully defined. At any other angle it also gets a horizontal construction line, and its angle becomes a dimension from that line on closing. Returns the ids of its entities.

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": {
      "x": "<x>",
      "y": "<y>",
      "centre_distance": "<centre_distance>",
      "width": "<width>"
    },
    "name": "draw_slot"
  }
}

Input Schema

NameRequiredDescriptionDefault
xYesX of the slot's centre
yYesY of the slot's centre
unitNomm, cm, m, inch or ft
angleNoDirection of the slot, degrees from +X (default 0)
widthYesWidth of the slot
centre_distanceYesDistance between the centres of the two end arcs

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/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 well: it discloses side effects the agent could not otherwise predict (auto-added horizontal/vertical relations, origin tie, dimensions created on sketch close, extra construction line at non-axis angles) and states the return value. It omits failure behavior (e.g. what happens with no open sketch) and how `unit` is applied.

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?

It is front-loaded with geometry, then parameters, then downstream modeling consequences, so an agent can stop reading early. Some sentences are convoluted ('unless set first: a slot on the origin is then fully defined'), costing clarity, but no sentence is 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 6-parameter geometry tool with no output schema, the description covers construction behavior, dimensional consequences, and the return value ('the ids of its entities'). It is nearly complete; only error/edge conditions and unit handling are unaddressed.

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: `width` is the full slot width and equals twice the end radius (which becomes the dimension), `centre_distance` is between arc centres, and `angle` defaults to 0 = horizontal. The only unexplained parameter is `unit`, which is left entirely to the schema.

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 opens with a specific verb and resource ('Add a straight slot to the open sketch') and then defines the geometry ('two half circles joined by two lines, around a construction centreline'), which is unambiguous and clearly distinct from the line/arc/circle siblings.

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 states the precondition ('the open sketch') and explains the consequences that would drive a choice of angle or placement (relations at 0/90, tie at origin, extra construction line at other angles). It does not name an alternative tool or say when not to use this one, so it falls short of 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