Skip to main content
Glama
FullyDefined – AI for SOLIDWORKS

FullyDefined – AI for SOLIDWORKS

select_faces

Selects solid body faces by geometry—points, face IDs from list_faces (stale IDs refused), or flat-face normal—so AI apps can target faces regardless of view.

Instructions

Select body faces by geometry (the view does not matter): by points (the face containing each point), face_ids from list_faces (refused if the geometry changed since it listed them), or normal (every flat face facing +x, -x, +y, -y, +z or -z).

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": "select_faces"
  }
}

Input Schema

NameRequiredDescriptionDefault
unitNomm, cm, m, inch or ft
appendNoAdd to the current selection instead of replacing it
normalNoSelect every flat face with this outward normal
pointsNoModel points inside the faces to select
face_idsNoFace ids from list_faces
toleranceNoHow far a point may be from its face (default 0.5 mm)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior3/5

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

With no annotations, the description carries the burden of behavioral disclosure. It usefully reveals that face_ids are refused after geometry changes and that view does not affect selection, but it does not describe selection replacement behavior, invalid-point handling, or empty-result behavior.

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 a single front-loaded sentence with no filler. The nested parentheticals make it slightly dense, but every clause contributes to distinguishing the selection modes and the face_ids precondition.

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 six-parameter selection tool with no required parameters, no output schema, and no annotations, the description covers the core modes and an important failure condition. Remaining details such as tolerance defaults and append semantics are left to the schema, which is acceptable given full schema coverage.

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

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is already 100%, so the baseline is 3. The description adds meaningful semantic detail by explaining that points select the containing face and that normal selects every flat face with the specified outward normal, going beyond the schema's terse parameter descriptions.

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 states a specific verb and resource: 'Select body faces by geometry.' It then distinguishes the three selection modes, points, face_ids, and normal, and clarifies that view does not matter, making the tool's purpose unambiguous relative to sibling tools like select_edges.

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 explains the available selection approaches and gives a concrete precondition for face_ids: they are refused if geometry changed since list_faces. It does not explicitly compare against select_edges or state when not to use this tool, but the face-specific purpose is clear.

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