Skip to main content
Glama
FullyDefined – AI for SOLIDWORKS

FullyDefined – AI for SOLIDWORKS

draw_line

Adds a line to an open SOLIDWORKS sketch at exact coordinates without snapping or automatic relations, joining shared endpoints and returning the new entity ID.

Instructions

Add a line to the open sketch at exactly the coordinates given: no snapping and no automatic relations. Lines that share an endpoint are joined. In a part, a line that touches nothing when the sketch is closed gets its length as a dimension (a line in a chain does not). Returns the id of the new entity.

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": {
      "x1": "<x1>",
      "y1": "<y1>",
      "x2": "<x2>",
      "y2": "<y2>"
    },
    "name": "draw_line"
  }
}

Input Schema

NameRequiredDescriptionDefault
x1YesX of the start point
x2YesX of the end point
y1YesY of the start point
y2YesY of the end point
unitNomm, cm, m, inch or ft

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, the description carries the full burden, and it does substantial work: it discloses that no snapping or automatic relations occur, that shared endpoints are joined, that isolated lines get an auto-dimension on sketch close in a part (but chained lines do not), and that the new entity's id is returned. Gaps remain around failure modes (no open sketch, invalid unit) and whether the auto-dimension is editable or suppressible.

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?

Four short sentences, front-loaded with the action and its most decision-relevant constraint (no snapping, no relations). The parenthetical about chained lines is dense but earns its place by disambiguating the dimension rule; little is wasted.

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 5-parameter geometry-mutation tool with no annotations and no output schema, the definition covers creation semantics, side effects (joining, auto-dimensioning), and the return value. Only the precondition for an active sketch and unit defaulting are left implicit.

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 parameter descriptions already explain x1/y1/x2/y2 and the unit string. The description adds meaningful interpretation (coordinates are honored exactly, no snapping), but says nothing about the unit parameter's default or valid interaction with the sketch's unit system.

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 ("Add a line to the open sketch") plus the exact placement policy ("exactly the coordinates given: no snapping and no automatic relations"), which distinguishes it from sibling draw_* tools that may snap or auto-constrain. An agent can tell what this creates and how it differs without opening another schema.

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

Usage Guidelines3/5

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

Usage is implied rather than stated: "the open sketch" signals a precondition (a sketch must be active), and the part-vs-chain note hints at context where this tool matters. However, no explicit when-to-use/when-not guidance is given and no alternative (e.g. draw_polyline, draw_rectangle) is named for cases where a line is the wrong primitive.

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