Skip to main content
Glama
danielproxd2

MCP_CAD

by danielproxd2

clarify_autoparts_intent

Resolves ambiguous Mexican-Spanish autoparts terms by returning a primary geometric archetype, alternatives, typical dimensions, and a disambiguation question to clarify user intent before modeling.

Instructions

Devuelve interpretaciones autoparts para un término en español/spanglish.

Phase 2 / Layer 2: cuando un usuario use un término informal de autopartes ('rin', 'buje', 'soporte', 'brida', 'cubo', 'flecha', 'polea', 'tapa', 'caja', 'gancho', 'balero', etc.) y necesites confirmar qué arquetipo geométrico quiere ANTES de proponer un plan, llama esta herramienta para obtener el mapeo curado.

Devuelve:

  • primary_archetype: la interpretación más común

  • alternative_archetypes: otras lecturas razonables

  • typical_dimensions: rangos esperados (mm/grados/conteos)

  • disambiguation_question: pregunta exacta para el usuario

[en: Look up an informal Mexican-Spanish autoparts term and get its curated geometric interpretation — primary archetype + alternatives + typical dim ranges + a ready-to-ask disambiguation question — use it to ground your interpretation when the user's request hinges on an ambiguous term. v1 vocabulary is Mexican-Spanish-specific and fixed in code; v1.1 may make it customer-extensible.]

Args: term: The Spanish / Spanglish term to look up. Case- and accent-insensitive ('Rin', 'rin', 'RIN' all match).

Returns: On match: { "term": str, # canonical spelling "primary_archetype": str, # internal handle "primary_description": str, # Spanish description "alternative_archetypes": [str, ...], "alternative_descriptions": [str, ...], "typical_dimensions": {key: [min, max], ...}, "disambiguation_question": str, "notes": str, "found": True, } On miss: { "term": str, "found": False, "fallback": str, # what to do instead "available_terms": [str, ...], # what IS in the glossary }

Caveat: this v1 vocabulary is Mexican-Spanish autoparts only. Argentine, Brazilian, or Peninsular Spanish usage may differ. Customers wanting their own vocabulary need v1.1 customer-config support.

Caveat: NOT all terms have a clean primary archetype. Generic terms like 'soporte', 'caja', 'balero', 'tornillo', 'rosca' map to 'ambiguous' or 'needs_custom_modeling' — use the disambiguation_question to narrow down.

Example — disambiguating 'rin' before building geometry: intent = clarify_autoparts_intent("rin") # → primary_archetype="wheel_rim", # alternatives=["wheel_hub_disc", "brake_rotor"], # typical_dimensions={od_mm: [330, 560], pcd_mm: [98, 120], ...} # Use the disambiguation_question to confirm the reading with # the user before any geometry runs.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
termYes
Behavior5/5

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

With no annotations, the description fully shoulders behavioral disclosure. It details return structures for match and miss, caveats about Mexican-Spanish specificity, terms that are generic or ambiguous, and mentions version limitations (v1 vs v1.1). 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 longer but well-structured with sections for use case, return values, caveats, and example. Information is front-loaded with the core purpose in Spanish and English. Every sentence adds value, but the dual-language nature slightly increases length.

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 1 parameter, no output schema, and no annotations, the description covers purpose, parameters, return structures (both match and miss), caveats, and example usage. It is fully complete for the tool's complexity and context signals.

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% (no description in schema), so description adds all meaning. It thoroughly explains the 'term' parameter: case- and accent-insensitive, and specifies the context (Spanish/Spanglish autoparts term). This far exceeds baseline and compensates for lack of schema description.

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 that the tool returns curated geometric interpretations for informal Spanish/Spanglish autoparts terms, specifying the verb 'look up' and resource 'autoparts terms'. It distinguishes itself from sibling CAD/modeling tools by being a disambiguation/interpretation step before proposing a plan.

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 instructs to use in Phase 2 / Layer 2 when a user uses an informal term and interpretation is needed before proposing a plan. Provides example terms and emphasizes the need to confirm geometric archetype via the disambiguation question. Though no explicit 'do not use', the context and caveats effectively guide appropriate usage.

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