Skip to main content
Glama
danielproxd2

MCP_CAD

by danielproxd2

list_edges

Enumerate edges of solid bodies with midpoint coordinates to enable spatial reasoning for fillet and chamfer operations.

Instructions

Listar aristas — enumerate edges of one or all solid bodies.

Returns one dict per edge with: - index: 0-based per-body. NOT durable across rebuilds. - body_name: which body the edge belongs to. - type: "line" | "circle" | "other" - midpoint_mm: [x, y, z] in mm. DURABLE reference for fillet/chamfer. None for closed-loop edges (full circles) — a circle has no canonical midpoint. For those, pass edge_indices to fillet/chamfer instead of edge_midpoints_mm. Partial arcs (post-fillet corner arcs) and line edges DO have midpoints. - length_mm: edge length in mm (None for closed loops).

Args: body_name: If given, return only edges of that body. Else return edges of every solid body in the active part.

Use case: pre-fillet/pre-chamfer LLM workflow. The LLM enumerates edges, reasons spatially ("the four top edges have z=10mm"), then passes midpoints to fillet() / chamfer().

Caveat: in this SolidWorks binding, edges can't be selected by name string in part-doc context — coordinate matching is the only durable address. Use the midpoint values returned here verbatim; don't recompute them in the LLM.

Example — list every edge in the active part: edges = list_edges() # edges = [{"index": 0, "body_name": "Saliente-Extruir1", # "type": "line", "midpoint_mm": [0, 0, 5], ...}, ...]

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
body_nameNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

With no annotations, the description fully discloses behavioral traits: index instability across rebuilds, midpoint being null for closed-loop edges, and the inability to select edges by name string. It explains durable vs non-durable references.

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?

The description is detailed and well-organized with sections for return values, args, use case, caveat, and example. While slightly lengthy, every sentence adds value. The structure aids comprehension.

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?

Given the tool's simplicity (one optional parameter) and the presence of an output schema, the description thoroughly covers return fields, use case, caveats, and parameter behavior. It is complete for agent invocation.

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?

The sole parameter 'body_name' has 0% schema description coverage, but the description fully explains its effect: when given, returns edges of that body; otherwise returns edges of all bodies. This adds complete meaning.

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?

The description clearly states it enumerates edges of one or all solid bodies, with specific return fields. It distinguishes from sibling tools like list_faces and fillet/chamfer by providing the use context.

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 explicitly guides use for pre-fillet/pre-chamfer workflows and advises using midpoint values verbatim. It does not list exclusions but provides a caveat about edge selection limitations, offering practical guidance.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/danielproxd2/solidworks-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server