Skip to main content
Glama
FullyDefined – AI for SOLIDWORKS

FullyDefined – AI for SOLIDWORKS

list_components

List the top-level components of the active assembly with names, files, fixed/floating status, origins, bounding boxes, and mates to inspect assembly structure and subassemblies.

Instructions

List the top-level components of the active assembly: name, file, fixed or floating, rigid or flexible for a sub-assembly, the position of the origin (and axes, if rotated) in the assembly, bounding box, and mates. A part inside a sub-assembly is addressed as 'Sub-1/Part-2'.

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_components"
  }
}

Input Schema

NameRequiredDescriptionDefault
unitNomm, cm, m, inch or ft

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations present, the description carries the full disclosure burden; it does state the key behavioral boundary that only top-level components are returned and gives the 'Sub-1/Part-2' addressing convention for nested parts. It omits what happens when no assembly is active, whether hidden or suppressed components are included, and whether results are paginated or ordered.

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?

Two sentences, both earning their place: the first front-loads the scope and the full field list, the second resolves the one ambiguity (how nested parts are addressed). Dense but no filler.

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?

There is no output schema, so the description must describe return values, and it does so field by field for a read tool whose name already signals non-mutation. The remaining gap is error/precondition behavior when no assembly is open, which matters for an agent invoking this blind.

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% for the single optional 'unit' parameter, so the schema already documents the allowed values. The description implies unit-dependent output in the mention of origin position and bounding box but never connects that to the unit parameter, adding no meaning beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

"List the top-level components of the active assembly" gives a specific verb and a precisely scoped resource, and the enumeration of returned fields (name, file, fixed/floating, rigid/flexible, origin position, bounding box, mates) makes the result set unambiguous. It does not name any sibling it contrasts with, and siblings such as list_mates and list_features overlap on some of the same data, so the differentiation is left implicit.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied through the scope phrase "of the active assembly," which hints that an assembly document must be active, but no prerequisites are stated. There is no guidance on when to prefer this over list_mates or list_features, nor any exclusion such as how nested parts are handled beyond the one addressing example.

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