Skip to main content
Glama
SolidWorks MCP Python

SolidWorks MCP Python

by locense

Select Face Edges

select_face_edges
Idempotent

Selects every edge of one face in the active part by point, side, or plane, so fillet or chamfer operations can run without edge names.

Instructions

Select every edge of one face of the active part, ready for add_fillet or add_chamfer with no edge names.

Pick the face with one of point (a point on it, mm), side (top, bottom, front, back, right, left or +X..-Z; the furthest flat face that way) or plane (the face lying on that plane). edge_type narrows to linear or circular edges (hole rims). Needs: an open part. Changes: the selection only. Returns: data with face, edges, selected_edges and selection_count.

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": {
      "input_data": "<input_data>"
    },
    "name": "select_face_edges"
  }
}

Input Schema

NameRequiredDescriptionDefault
input_dataYesThe face. Give exactly one of `point`, `side` or `plane`; `edge_type` (all) and `append` (off) have defaults.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations say readOnlyHint=false with destructiveHint=false; the description explains that gap precisely with 'Changes: the selection only' (state mutated, geometry untouched) and adds the 'open part' prerequisite. It does not describe failure modes (e.g., no matching face) or edge cases around replacing an existing selection, so a 4 rather than 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the outcome, then selector options, then the compact Needs/Changes/Returns triad. No sentence is redundant given the information value; the structure maps cleanly onto what an agent needs to decide, invoke and verify.

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 tool with a nested input object, a precondition and a state mutation, the description covers selection mode, prerequisites, side effects and return keys, and an output schema exists to carry the return shape. Missing only error/empty-result behavior, which is the one remaining gap for reliable invocation.

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 the schema already defines side, plane, point, append and edge_type. The description restates the same semantics in prose ('the furthest flat face that way', 'hole rims') without adding syntax, units beyond mm, or interaction rules the schema lacks, 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?

The first sentence gives a specific verb and resource ('Select every edge of one face of the active part') and immediately frames the outcome ('ready for `add_fillet` or `add_chamfer` with no edge names'), which distinguishes it from generic selection siblings. An agent knows exactly what it gets 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?

It names the three mutually exclusive selectors (point, side, plane) and explains what each targets, plus a precondition ('Needs: an open part'). It gives downstream usage context (fillet/chamfer) but does not say when to prefer this over other selection-oriented siblings such as select_feature, so it stops short of full alternative routing.

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