Skip to main content
Glama
cadcraft-electrical-mcp

cadcraft-electrical-mcp

build

Generate complete electrical drawing sets as DXF, multipage PDF, optional DWG, fabrication back-plate DXF, XLSX/CSV lists, and PNG previews, returning file paths, pages, and validation results.

Instructions

Generate the drawing set: DXF (all sheets), multi-page PDF (via CADCraft), optional DWG, the 1:1 fabrication DXF of the back plate, XLSX/CSV lists and PNG previews of the sheet numbers in previews. Returns file paths, page list and a validation summary.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "build"
  }
}

Input Schema

NameRequiredDescriptionDefault
dwgNo
pdfNo
reportsNo
previewsNo
include_coverNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations declare a mutating, non-idempotent, open-world operation, and the description adds useful context by naming the external dependency ('via CADCraft') and the artifact set produced. However, it does not disclose whether existing output files are overwritten, whether CADCraft must already be opened/connected, or how long a build runs — meaningful gaps for a write tool with destructiveHint=false.

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?

Two sentences, front-loaded with the primary action and the artifact list, with no filler. The parenthetical enumerations are dense but each item maps to a real output, though the trailing list grows long enough to be slightly harder to scan.

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?

An output schema exists, so the description's return summary is a bonus rather than a necessity, and the artifact enumeration is solid. Still, for a five-parameter, open-world build tool with zero parameter documentation and no stated prerequisites or file-overwrite behavior, an agent could invoke it incorrectly without discovering the problem until after generation.

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%, so the description carries full burden, but it only partially compensates: `dwg` is explicitly optional, `pdf` is implied, and 'PNG previews of the sheet numbers in `previews`' hints at the `previews` list. It never explains `include_cover` or clarifies that 'XLSX/CSV lists' corresponds to the `reports` flag, leaving two of five parameters undocumented anywhere.

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 ('Generate') and a concrete resource ('the drawing set'), then enumerates exactly which artifacts are produced: DXF for all sheets, multi-page PDF, optional DWG, 1:1 fabrication DXF, XLSX/CSV lists, and PNG previews. This separates it cleanly from siblings like `reports` or `sheet_preview`, which cover only a subset of these outputs.

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?

Usage is only implied: an agent can infer this is the end-of-pipeline export step, but the description never says when to call it versus `reports`, `sheet_preview`, or `cadcraft_execute`, nor what prerequisites must hold (project open, CADCraft available). No exclusions or ordering guidance are given.

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