Skip to main content
Glama
cadcraft-electrical-mcp

cadcraft-electrical-mcp

library_import_model

Cleans vendor DXF/DWG front-view models into 1:1 mm catalog blocks by removing CADENAS ATTDEFs, connection points, and dimensions, converting DWG, and moving the lower-left corner to 0,0.

Instructions

Clean a vendor 2D model (DXF or DWG front view) into a 1:1 mm block and add it to your catalog.

Removes CADENAS ATTDEFs, connection points and (by default) dimensions, converts DWG through CADCraft, moves the lower-left corner to 0,0. Use target_width_mm (real device width) when the file is not drawn in mm. The cleaned DXF goes to /library.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "source_path": "<source_path>",
      "catalog_id": "<catalog_id>"
    },
    "name": "library_import_model"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNogeneric
mountNodin_rail
portsNo
scaleNo
catalog_idYes
keep_textsNo
descriptionNo
part_numberNo
source_pathYes
manufacturerNo
keep_dimensionsNo
target_width_mmNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations only declare the generic profile (mutation, non-idempotent, non-destructive), while the description adds real substance: ATTDEFs, connection points and dimensions are stripped, DWG is routed through CADCraft, the lower-left corner is re-origined to 0,0, and output lands in <workspace>/library. It does not say what happens on re-import of an existing catalog_id or whether the source file is modified, which keeps it off a 5.

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?

Front-loaded with the outcome, then the transformation details and the one parameter caveat — no filler sentences. The line-wrapped formatting is slightly awkward but every clause carries information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Return values are covered by an output schema and the processing pipeline is well described, so the core call is answerable. However, for a 12-parameter mutation with zero schema descriptions, the definition leaves most inputs unexplained and says nothing about failure modes (unreadable DWG, missing catalog_id) or idempotency, so it is only adequately complete.

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

Parameters2/5

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

Schema description coverage is 0% across 12 parameters, so the description must carry the meaning, yet it only explains `target_width_mm` and indirectly `keep_dimensions` ('by default' dimensions are removed). Fields like `scale` vs `target_width_mm`, `ports`, `kind`, `mount`, `keep_texts`, and the metadata fields are left entirely to their bare names, and the interaction between `scale` and `target_width_mm` is never resolved.

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?

States a specific verb and resource ('Clean a vendor 2D model (DXF or DWG front view) into a 1:1 mm block and add it to your catalog') plus the transformation pipeline. An agent can distinguish this import/normalization tool from library_search or device_add without opening the schema.

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?

Gives one conditional hint — use `target_width_mm` when the file is not drawn in mm — which is parameter guidance rather than tool-selection guidance. It never says when to prefer this over cadcraft_execute or device_add, nor what preconditions (valid DXF/DWG, existing catalog_id) must hold, leaving usage largely implied.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.