Skip to main content
Glama
FullyDefined – AI for SOLIDWORKS

FullyDefined – AI for SOLIDWORKS

list_component_sketches

Lists sketches of a component in the active assembly, then returns a chosen sketch's points and segments in assembly coordinates with IDs for mates and measurements.

Instructions

List the sketches of one component of the active assembly. Given a sketch name, list that sketch's points and segments (line / arc / circle with start, end, centre, radius) in ASSEMBLY coordinates. The ids are the point_id / segment_id that add_mate and measure_distance take. They follow SolidWorks' order for a finished sketch, which is NOT the ids list_sketch_entities gave while drawing. Each point has an 'of' field saying what it is: ['2:center'] is the centre of circle or arc 2, ['1:end', '3:start'] a corner shared by two segments, [] a point made with draw_point. Read-only.

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": {
      "component": "<component>"
    },
    "name": "list_component_sketches"
  }
}

Input Schema

NameRequiredDescriptionDefault
unitNomm, cm, m, inch or ft
sketchNoSketch name. Leave out to get the list of sketch names.
componentYesComponent name from list_components, or a path into a sub-assembly

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/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 declares 'Read-only', specifies that coordinates are in ASSEMBLY coordinates, discloses the ordering quirk (SolidWorks' finished-sketch order, not the drawing-time order), and explains the 'of' field semantics with examples. That is well beyond what any structured field provides.

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?

Front-loaded with the primary action, then progressively tighter detail on ids and the 'of' field; the closing 'Read-only' is well placed. It is information-dense and slightly packed in the middle, but no sentence is filler.

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?

There is no output schema, so the description must explain return values, and it does: field lists for points and segments, the meaning of each 'of' entry with three example cases, and coordinate frame. For a three-parameter read tool this covers everything an agent needs to call and interpret it.

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 all three parameters are already documented, including the 'leave out sketch to get names' behavior which the description repeats. The description adds downstream meaning about the returned ids but says nothing extra about 'component' (path form) or 'unit' beyond the schema, so baseline 3 applies.

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 ('List the sketches of one component of the active assembly') and describes both modes: component-only returns sketch names, component+sketch returns points and segments with their fields. It explicitly contrasts itself with the sibling list_sketch_entities, noting the ids differ from what that tool returned during drawing.

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?

The description tells the agent what the ids are for ('the point_id / segment_id that add_mate and measure_distance take') and that omitting the sketch name yields the name list, which is concrete routing guidance. It stops short of an explicit when-not-to-use statement, though the list_sketch_entities contrast implicitly warns against using that tool's ids for downstream calls.

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