Skip to main content
Glama
danielproxd2

MCP_CAD

by danielproxd2

get_bounding_box

Returns the overall axis-aligned bounding box of the active part or assembly, including min/max corners, size, and center in mm. Use it for stock selection, sanity checks, or nesting calculations.

Instructions

Caja envolvente — overall axis-aligned bounding box of the active part OR assembly, in mm. Read-only — does not modify the document.

Returns a dict in mm-native units (part frame): - min_mm (list[float], 3): [x, y, z] of the minimum corner. - max_mm (list[float], 3): [x, y, z] of the maximum corner. - size_mm (list[float], 3): [dx, dy, dz] overall extents (max − min). This is the part's bounding-box footprint. - center_mm (list[float], 3): [x, y, z] box center ((min + max) / 2).

Unions the bounding boxes of every solid body, so multi-body parts report the combined envelope.

Common autoparts uses: - Stock selection: size_mm tells you the minimum bar / plate / billet the part fits in. - Sanity check after a build: confirm the part's overall dimensions match what was intended BEFORE trusting the feature tree (cheap verification, no screenshot needed). - Nesting / fixturing envelope.

Example — verify a plate's footprint: bbox = get_bounding_box() assert abs(bbox["size_mm"][0] - 100) < 0.5 # expected 100mm wide

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior5/5

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

The description explicitly states the tool is read-only and does not modify the document. It explains that for multi-body parts, the bounding box unions all solid bodies. Since no annotations are provided, the description fully covers behavioral traits.

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 well-organized with a summary, field list, behavioral note, use cases, and an example. It is concise without superfluous information, though slightly longer than necessary for a zero-parameter tool.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no parameters and no output schema, the description is complete. It explains what the tool does, its return values, behavior for multi-body parts, and practical applications. No additional information is needed.

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?

The input schema has no parameters, so schema coverage is 100% trivially. The description adds value by detailing the return dict structure (min_mm, max_mm, size_mm, center_mm) and their meanings, compensating for the lack of output schema.

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 clearly states the tool returns the axis-aligned bounding box of the active part or assembly in mm. It specifies the output fields and distinguishes from other tools by focusing solely on bounding box retrieval. No sibling tool serves this purpose.

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?

The description provides common autoparts uses like stock selection, sanity checks, and nesting. While it doesn't explicitly list when not to use this tool, the use cases are clear and there are no direct alternatives among siblings.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/danielproxd2/solidworks-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server