Skip to main content
Glama

build_part_index

Index SolidWorks .SLDPRT parts in a local folder, extracting name, bounding box, mass, and bore inventory into a SQLite catalog for offline use. Skips unchanged files for incremental indexing.

Instructions

Indexa una carpeta de piezas .SLDPRT en un catálogo LOCAL (PDM-lite).

Abre cada pieza EN SERIE (solo lectura), toma nombre/bbox/masa/inventario de barrenos, la cierra, y guarda todo en mcp_cad_index.sqlite DENTRO de la carpeta — nada sale del equipo (sin red, sin telemetría). Incremental: archivos sin cambios (mtime+tamaño) se saltan; rebuild=True relee todo. Corre con SolidWorks desocupado: abre y cierra documentos.

Args: folder: carpeta raíz (búsqueda recursiva; ignora temporales ~$). rebuild: True relee también los no-modificados. max_parts: tope de archivos por corrida.

Returns: {indexed, skipped_unchanged, removed_stale, failed[], parts, bores, db_path, truncated_at_max_parts}.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
folderYes
rebuildNo
max_partsNo
Behavior5/5

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

With no annotations, the description fully discloses behavior: opens parts in series read-only, extracts metadata, no network, incremental, and rebuild option. 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two well-structured paragraphs with front-loaded purpose. Every sentence adds value, no redundancy.

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?

Despite no output schema, the description lists return fields. For a tool with 3 parameters and simple behavior, it is complete.

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

Parameters5/5

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

Schema coverage is 0%, so description fully explains each parameter: folder (recursive, ignores temp files), rebuild (re-reads all), max_parts (limit). Adds significant meaning.

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 indexes a folder of .SLDPRT parts into a local catalog, distinguishing it from sibling tools that focus on modeling operations.

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?

Provides clear context on incremental vs rebuild mode and advises running when SolidWorks is idle, but does not explicitly list when to avoid using the tool.

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