Skip to main content
Glama

List Assembly Parts

list_assembly_parts
Read-only

Retrieves the name, type, linked target, position, and volume of each part in a FreeCAD assembly so you can inspect its structure.

Instructions

List parts of an assembly: name, type, linked-target name, position, volume.

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": {
      "assembly": "<assembly>"
    },
    "name": "list_assembly_parts"
  }
}

Input Schema

NameRequiredDescriptionDefault
assemblyYes
workspaceNoRun this call in this named workspace

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.5.7
    • addedInput schema / properties / workspace
      Added value: +{
      +  "default": "",
      +  "description": "Run this call in this named workspace",
      +  "title": "Workspace",
      +  "type": "string"
      +}
  2. First observed

TDQS

B3.2/5.0
Behavior3/5

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

The readOnlyHint and openWorldHint annotations already communicate that this is a safe, local read operation. The description adds useful behavioral context by listing what information is returned, but it does not describe error behavior, pagination, ordering, or what happens if the assembly identifier is invalid.

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?

The description is a single compact sentence that front-loads the operation and immediately enumerates the returned fields. Every phrase adds useful information without repetition.

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?

Because there is no output schema, the description appropriately lists the returned fields. Given the tool's low complexity and existing read-only annotations, it is mostly complete, though it could say more about the assembly identifier and workspace behavior.

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

Parameters2/5

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

Schema description coverage is only 50%: the workspace parameter is documented, but the required assembly parameter has no schema description. The description refers to 'an assembly' but does not explain the expected identifier format, path, name, or how it is resolved, so it does not compensate for the missing parameter documentation.

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?

The description uses a specific verb and resource: it lists parts of an assembly. It also names the returned fields (name, type, linked-target name, position, volume), which clarifies the operation beyond the bare tool name. It does not explicitly distinguish itself from nearby sibling tools such as list_objects or list_faces, so it is clear but not fully differentiated.

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

Usage Guidelines2/5

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

The description gives no explicit guidance about when to use this tool versus alternatives, nor does it state prerequisites or exclusions. Usage is only implied by the phrase 'parts of an assembly'.

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