Skip to main content
Glama
danielproxd2

MCP_CAD

by danielproxd2

get_active_part_info

Retrieve metadata from the active SolidWorks part: name, modification status, features with dimensions, and solid bodies. Use this to inspect the part and obtain body names for subsequent modifications.

Instructions

Return metadata about the currently active SolidWorks part.

Includes the part name, whether it has been modified since open, the list of features with their dimensions, and the list of solid bodies (typically one per part; multi-body parts have several). Use this to inspect what's in the current part before suggesting modifications, and to discover the body names you need for extrude_cut's target_bodies / reference_name arguments.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior4/5

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

No annotations provided, so description carries full burden. It discloses the return contents (part name, modified status, features, bodies) and implies read-only behavior, but doesn't mention potential limitations like performance impact.

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?

Three well-structured sentences: purpose, contents, usage guidance. No extraneous words, front-loaded with key information.

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?

Given no output schema and a simple tool, description adequately covers what the tool returns and its purpose. Could mention prerequisite (part must be open) but implied by 'active part'.

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?

No parameters, so schema coverage is 100%. Description adds full meaning beyond the empty schema by detailing the information returned.

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?

Description uses a specific verb ('Return') and resource ('active SolidWorks part') and clearly distinguishes from siblings by mentioning its use for discovering body names needed for extrude_cut.

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

Usage Guidelines5/5

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

Explicitly states when to use (before modifications) and references a specific sibling tool (extrude_cut) to provide context for body name discovery.

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