Skip to main content
Glama
solidworks-mcp

solidworks-mcp

list_edges

Read-onlyIdempotent

Retrieve edges of the active part or of a specific feature with their type, midpoint, length, end points, and circle or arc data. Use these exact coordinates instead of guessing for fillets, chamfers, patterns, and edge selection.

Instructions

Edges of the active part (or only those of the faces created by 'feature'), each with its type, its mid-point (point_mm, lying ON the edge: pass it to fillet / chamfer edge_points, select_edge_at_point, circular_pattern axis_edge_point...), length, end points, and centre / diameter of circles and arcs. Use it instead of guessing coordinates.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_edges"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of edges returned
featureNo
edge_typeNoany

Output Schema

NameRequiredDescriptionDefault
countYes
edgesYes
totalYes
truncatedYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.1

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the safety profile is covered; the description adds genuinely new behavioral context, notably the guarantee that point_mm lies ON the edge (not merely near it), which is what makes the output safe to feed into fillet/chamfer. The notable omission is the default 80-edge cap and maximum 500, meaning an agent is not warned that a large model's edge list may be silently truncated.

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 dense sentence, front-loaded with the resource and scope, followed by the return payload and then the usage directive — appropriate ordering with no filler. The heavy parenthetical listing of consumer tools makes it slightly hard to scan, but every clause carries information.

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 an output schema present, the description does not need to enumerate return fields, and it wisely uses the space instead for the on-edge guarantee and downstream routing. It is essentially complete for a read-only enumerator, with the truncation behavior of 'limit' being the one remaining gap an agent would need.

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 coverage is only 33%, and the description compensates for the weakest parameter by explaining 'feature' as the filter on faces created by that feature, which the schema leaves empty. However, 'limit' (the truncation control) gets no mention in the description despite being the one parameter whose semantics matter most for correctness, and 'edge_type' is only implied by 'each with its type'.

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 edges of the active part) plus the exact payload each edge carries: type, mid-point, length, end points, and circle/arc centre and diameter. The lead clause also defines the scope variant (all edges vs. only those of faces created by 'feature'), which makes it immediately distinguishable from the sibling geometry enumerators such as list_faces.

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 concrete downstream routing: the returned point_mm should be passed to fillet/chamfer edge_points, select_edge_at_point, and circular_pattern axis_edge_point, and closes with an explicit prohibition ('Use it instead of guessing coordinates'). It does not state when *not* to use it (e.g., when only face-level data is needed, use list_faces), so it stops short of full alternative coverage.

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