Skip to main content
Glama
FullyDefined – AI for SOLIDWORKS

FullyDefined – AI for SOLIDWORKS

list_faces

Lists solid body faces with ID, type, area, outward normal, bounding box, and a point for inspection and selection; IDs expire after geometry changes, so re-list before selecting.

Instructions

List the faces of the solid body: id, type (plane / cylinder / other), area, outward normal, bounding box and a point on each face. Ids hold only until the geometry changes: select_faces 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_faces"
  }
}

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

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, the description carries the full burden and does disclose the key behavioral trait: id volatility across geometry changes and the resulting failure mode in select_faces. It also explains the default output shape and the token tradeoff of compact. It does not mention whether a body must be active/selected or what happens with no body present.

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?

Three tight sentences, front-loaded with the returned fields, then the id-lifetime caveat, then the output-format note. Dense but every clause carries information; the parenthetical '(list again)' is slightly clipped but functional.

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?

No output schema exists, so the description must describe return values, and it does so field by field, plus the compact vs object row shape. Combined with the id-lifetime warning, an agent has enough to call and interpret it; only preconditions for invocation are unstated.

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 both parameters are already documented, and the description's compact explanation largely restates the schema's own wording. The unit parameter is never mentioned in the description, so no meaning is added beyond the schema. 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?

States a specific verb and resource (list the faces of the solid body) and enumerates exactly what each item contains: id, type, area, outward normal, bounding box, point. The type enumeration (plane / cylinder / other) further pins down the resource, so an agent can distinguish it from select_faces or list_component_faces without opening a 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 a concrete re-use rule: ids are only valid until the geometry changes, and select_faces will refuse them after a change, so the agent should list again. That is real when-to-use guidance tied to a sibling. It stops short of stating prerequisites (e.g. an active document or selected body) or when to prefer list_component_faces.

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