Skip to main content
Glama
danielproxd2

MCP_CAD

by danielproxd2

query_part_library

Find similar parts in a local catalog using filters like text, bore diameter, mass, and envelope to avoid redesigning existing components.

Instructions

Busca piezas parecidas en el catálogo local — '¿ya hicimos algo así?'.

Filtros combinables (AND): texto libre en español (por tokens, ignora acentos; busca en nombre de archivo/pieza/notas), Ø de barreno requerido ± tolerancia, ventana de masa, y envelope [x,y,z] mm donde la pieza debe caber (sin importar orientación). Read-only sobre el índice; corre build_part_index primero en esa carpeta.

Args: folder: carpeta ya indexada. text: p.ej. 'buje balero'. bore_diameter_mm: la pieza debe tener un barreno de este Ø. diameter_tol_mm: tolerancia del Ø. min_mass_g / max_mass_g: ventana de masa. fits_envelope_mm: [x, y, z] del material en bruto disponible. limit: máximo de resultados.

Returns: {count, results: [{filename, path, part_name, bbox_size_mm, mass_g, feature_count, cut_count, bores, notes, indexed_at}]}.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
textNo
limitNo
folderYes
max_mass_gNo
min_mass_gNo
diameter_tol_mmNo
bore_diameter_mmNo
fits_envelope_mmNo
Behavior4/5

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

The description explicitly states the tool is read-only ('Read-only sobre el índice'), which is critical for safety. It details the filter behavior (AND logic, tolerance, envelope). With no annotations provided, the description effectively communicates the non-destructive nature and search behavior.

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-structured with a clear purpose, filter explanation, argument list, and return format. It is front-loaded with the main goal. However, it is slightly verbose; the inline parameter explanations could be shortened if schema descriptions were provided.

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 tool complexity (8 parameters, no output schema, no annotations), the description provides comprehensive details: filter combinations, tolerance semantics, envelope orientation-agnostic behavior, indexing prerequisite, and a full return structure. Nothing essential is missing for an agent to correctly use this tool.

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?

With 0% schema description coverage, the description compensates by listing and explaining each parameter in the Args section, including examples (e.g., 'buje balero' for text). It adds meaning beyond the raw schema, though some parameters could use more detail on format (e.g., fits_envelope_mm).

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 clearly states the tool's purpose: searching for similar parts in a local catalog ('¿ya hicimos algo así?'). It provides a specific verb and resource, but does not explicitly differentiate from the sibling tool 'search_part_catalog', which may have overlapping functionality.

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 includes a prerequisite: 'corre build_part_index primero en esa carpeta' (run build_part_index first). It also states it is read-only. However, it does not provide guidance on when not to use this tool or suggest alternative tools for similar queries.

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