Skip to main content
Glama
FullyDefined – AI for SOLIDWORKS

FullyDefined – AI for SOLIDWORKS

draw_point

Add a sketch point at specified X/Y coordinates in the open SOLIDWORKS sketch for reference geometry, assembly mating, or measurement.

Instructions

Add a sketch point at x, y in the open sketch. A point is reference geometry: an extrude ignores it. In an assembly it can be mated to or measured from; list_component_sketches gives its id. list_sketch_entities shows such points under 'points'.

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>"
    },
    "name": "draw_point"
  }
}

Input Schema

NameRequiredDescriptionDefault
xYesX in sketch coordinates
yYesY in sketch coordinates
unitNomm, cm, m, inch or ft

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/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 disclose non-obvious behavior: points are reference geometry that feature operations ignore, and they are discoverable through list_sketch_entities under 'points'. It does not state what happens if no sketch is open, whether duplicate points are allowed, or what the call returns.

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?

Three short sentences with the action front-loaded and each sentence contributing new information (action, entity semantics, discovery route). The phrase 'list_component_sketches gives its id' is slightly ambiguous about what 'its' refers to, a minor clarity cost.

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 three-parameter tool with full schema coverage and no output schema, the description covers purpose, entity semantics, and discovery. The main omission is any statement about the return value or failure behavior when no sketch is active, which matters since no output schema exists to fill that gap.

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 x, y, and unit are already documented in the schema; the description only restates the coordinate context. Baseline 3 applies because the schema does the semantic work for all three parameters.

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 sketch point at x, y') plus the scope ('in the open sketch'), which immediately separates it from the draw_line/draw_arc/draw_circle siblings. The follow-up sentence clarifies what kind of entity is produced ('reference geometry'), removing any ambiguity about the result.

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?

Gives clear context for when a point is useful: extrude ignores it, but in an assembly it can be mated or measured, and it is visible via list_sketch_entities. It does not explicitly say when to prefer this over other sketch tools or what preconditions (an active sketch) must hold beyond the phrase 'in the open sketch'.

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