Skip to main content
Glama
hjbaard

SolidWorks-MCP

by hjbaard
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

list_edges

List a part's edges with index, type, length, ends, and line axis/midpoint; narrow by face, feature, bounding box, or min length to select edges for fillets or chamfers.

Instructions

List the part's edges: index, type, length, ends; lines also axis and midpoint.

Narrow it on a big part: face (a list_faces index, "#5"), feature (the edges of the faces it made), within_mm ([[x1, y1, z1], [x2, y2, z2]]: both ends inside), min_length_mm. Indices are always those of the whole part: use them with add_fillet/add_chamfer edges="2,5".

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
faceNo
featureNo
within_mmNo
min_length_mmNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.13.0
    • addedInput schema / properties / face
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Face"
+}
    • addedInput schema / properties / feature
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Feature"
+}
    • addedInput schema / properties / min_length_mm
      Added value: +{
+  "anyOf": [
+    {
+      "type": "number"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Min Length Mm"
+}
    • addedInput schema / properties / within_mm
      Added value: +{
+  "anyOf": [
+    {
+      "items": {},
+      "type": "array"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Within Mm"
+}
  2. First observedv0.4.0

TDQS

A4.4/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 delivers key behavioral context: what each returned edge includes, that lines additionally carry axis and midpoint, and critically that indices are always whole-part indices (stable regardless of filtering). It doesn't state read-only safety or error behavior, but the disclosed index semantics are a genuine behavioral trait beyond the schema.

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-loads the purpose and return shape, then the filters, then the index-usage note, with no filler sentences. The line break lands mid-clause ('face (a list_faces index, "#5")') and the density is high, but every sentence earns its place.

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?

With no output schema and no annotations, the description still covers the return fields, all filter parameters, and how the indices are consumed downstream, which is enough to invoke the tool correctly. It omits pagination/limits and error behavior on an invalid face/feature, minor gaps for a listing tool.

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

Parameters5/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 compensate fully, and it does: face is given the '#5' format and its source (a list_faces index), feature is defined as the edges of the faces it made, within_mm is given the explicit [[x1,y1,z1],[x2,y2,z2]] shape and 'both ends inside' semantics, and min_length_mm is self-describing. This is far richer than the empty 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?

States a specific verb and resource ('List the part's edges') and immediately enumerates the returned fields (index, type, length, ends, axis, midpoint), which distinguishes it from sibling listing tools like list_faces and list_bodies. An agent can tell exactly what this tool produces without opening the schema.

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?

Explicitly tells the agent to 'Narrow it on a big part' and lists the filter conditions for doing so, plus how the returned indices feed into add_fillet/add_chamfer. It lacks an explicit statement of when NOT to use it or a named sibling alternative, so it falls just 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