Skip to main content
Glama

query_part_library

Search a local indexed folder for similar CAD parts using filters like text, bore diameter, mass range, and bounding envelope. Returns matching files with metadata.

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?

No annotations are provided, so the description carries the full burden. It discloses read-only behavior, search mechanism (token-based, accent-insensitive, etc.), and combinable filters. It also describes the return structure. This is adequate for a query tool, though no rate limits or side effects are mentioned.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

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

The description is moderately concise but contains bilingual text (Spanish summary and English Args). The structure is logical, front-loading the purpose and then detailing parameters. Some sentences could be trimmed without losing clarity.

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 the complexity (8 parameters, no output schema), the description covers the necessary context: search functionality, filter combinations, prerequisite, and return fields. It is sufficiently complete for an agent to understand the tool's capabilities and limitations.

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?

Schema description coverage is 0%, so the description must compensate. It provides detailed explanations for each parameter in the Args section, including examples ('p.ej. 'buje balero'') and constraints ('la pieza debe tener un barreno de este Ø'). This adds significant meaning beyond the schema.

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 it searches for similar parts in the local catalog, using a specific verb and resource. It distinguishes the tool's purpose from siblings like 'search_part_catalog' by focusing on local indexed parts, but does not explicitly differentiate. The Spanish summary adds context.

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

Usage Guidelines3/5

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

The description mentions a prerequisite ('run build_part_index first') and that it is read-only. However, it lacks explicit guidance on when to use this tool versus alternatives like 'search_part_catalog' or when not to use it. The usage context is implied but not fully explicit.

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