Skip to main content
Glama

get_feature_inventory

Reads every feature in the SolidWorks part tree with per-cut details and bore inventory from geometry. Call before modifying multi-feature parts to verify unchanged features.

Instructions

Inventario completo de operaciones — one read of EVERY feature in the tree.

Per feature: name, type, dimensions, plus per-cut detail (kind, through, depth, diameter, internal) and the source of each value ('feature' | 'geometry' | 'addin'). On cuts, unknowns are explicit (through=None over COM, named in unverified); on non-cut features the N/A cut fields are omitted. occluded:true cuts cannot be verified by an iso render — check them with capture_views(section=...) / list_faces.

Also returns bores: a GEOMETRY-FIRST inventory of every cylindrical bore in the solid (Ø, axis, center, through/blind, and split=True when a slot crosses the bore — a clevis/fork, not a solid-hub hole), read from face geometry, not the feature tree. This catches what per-feature detail can't: a split pin hole, a bore shared across features, two bores in one cut.

USE BEFORE modifying any multi-feature part: enumerate every cut, change one, re-call, then confirm feature_count + the OTHER features are unchanged. The inventory is a contract. Read-only.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior5/5

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

With no annotations, the description fully covers behavioral traits: read-only nature, handling of unknowns ('through=None over COM'), occluded cuts needing verification via other tools, and the bores inventory derived from face geometry. No contradictions.

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 detailed and well-structured but slightly verbose. It front-loads the purpose and then elaborates on specifics. Every sentence adds value, though minor trimming could improve conciseness.

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 the complexity of the tool and absence of output schema, the description thoroughly explains the return structure: per-feature fields, bores fields, and edge cases (unverified, occluded). It covers all necessary context for an AI agent.

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 are defined, so schema coverage is 100%. The description adds no parameter info since none exist, meeting the baseline of 4.

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 it returns 'Inventario completo de operaciones — one read of EVERY feature in the tree' with detailed per-feature info and a separate bores inventory. It distinguishes from siblings like describe_feature or list_faces by its comprehensive scope.

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?

It explicitly advises to 'USE BEFORE modifying any multi-feature part' and provides a workflow: enumerate, modify, re-call, confirm. This gives clear context for when to use, though it doesn't explicitly mention alternatives.

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/MCP_CAD'

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