Skip to main content
Glama
solidworks-mcp

solidworks-mcp

sketch_point

Adds a point at specified x and y millimeter coordinates in the open sketch, creating a reference for dimensions or hole positions.

Instructions

Adds a sketch point at (x, y) mm in the open sketch (e.g. a reference for dimensions or a hole position).

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_mm": "<x_mm>",
      "y_mm": "<y_mm>"
    },
    "name": "sketch_point"
  }
}

Input Schema

NameRequiredDescriptionDefault
x_mmYes
y_mmYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.1

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare this is a non-read-only, non-destructive, non-idempotent, closed-world mutation, so the safety profile is mostly covered. The description usefully adds the precondition that a sketch must be open and that coordinates are in mm, but it says nothing about duplicate-point behavior (relevant given idempotentHint=false) or side effects such as consuming sketch entities or affecting sketch state.

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?

A single front-loaded sentence with the action, locus, and units first, and a short parenthetical for motivation. No filler; the only cost is that brevity leaves behavioral questions unanswered elsewhere.

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?

An output schema exists, so return values need not be described, and the tool itself is simple. Given the annotations cover mutation semantics, the main residual gap is the coordinate frame convention and duplicate handling, which are minor for a two-parameter creation tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must carry parameter meaning; it only supplies the unit (mm) for the two coordinates. It adds no clarification of origin, axis orientation, sign conventions, or valid range for x_mm and y_mm, leaving much of the two-parameter semantics to inference from the property names.

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?

States a specific verb and resource ('Adds a sketch point') plus the coordinate frame ('at (x, y) mm in the open sketch'), and the parenthetical clarifies what such a point is for. It does not explicitly distinguish itself from siblings like convert_point or sketch_line, so it falls short of a 5.

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?

The examples ('a reference for dimensions or a hole position') imply typical use cases but never state when to prefer this over convert_point, sketch_line, or a fully-defined-sketch workflow. Usage is inferred rather than instructed, and there are no exclusion conditions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.