Skip to main content
Glama
FullyDefined – AI for SOLIDWORKS

FullyDefined – AI for SOLIDWORKS

list_edges

Retrieve edge IDs, types, lengths, endpoints, midpoints, and radii/centers from a SOLIDWORKS solid body; optional filters narrow results by edge type or axis.

Instructions

List the edges of the solid body: id, type (line / circle / arc), length, end points, midpoint, and radius / centre for round edges. Filters are optional. Ids hold only until the geometry changes: select_edges refuses them after a change (list again). By default one short text line per item (fewer tokens); compact: false gives an object per item.

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
unitNomm, cm, m, inch or ft
compactNoOne short text line per row (same ids and values, fewer tokens); false gives an object per row
edge_typeNoOnly edges of this type
parallel_toNoOnly straight edges parallel to this model axis

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations supplied, the description carries the burden and does well: it discloses the id-volatility contract, the downstream failure mode in select_edges, and the default token-saving output shape. It stops short of stating which body/document is queried or how large result sets behave, which matters for a listing call with no annotations.

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 resource and returned fields, then the id-lifetime caveat, then the output-format note -- a deliberate information hierarchy. It is dense to the point of compression (semicolon chains, 'radius / centre'), but nearly every clause carries operational value.

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?

For a no-output-schema read tool, listing the return fields and the compact/object toggle fills exactly the gap the schema cannot. The remaining hole is scope -- which body or document the edges come from -- plus any limits on result size.

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 100%, so the schema already documents unit, compact, edge_type and parallel_to, and the baseline is 3. The description reinforces that filters are optional and explains the compact trade-off, but adds no new syntax or format guidance beyond the schema text.

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?

Specific verb and resource ('List the edges of the solid body') immediately followed by the exact returned fields: id, type, length, end points, midpoint, radius/centre. The parenthetical type enumeration (line/circle/arc) further pins down scope, so an agent can distinguish this from select_edges or list_faces 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?

Gives real usage context: filters are optional (so a bare call is valid), and it warns to re-list after geometry changes because select_edges will reject stale ids. It does not compare against sibling listing tools such as list_faces or list_component_faces, which leaves some 'which lister do I call' work to inference.

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