Skip to main content
Glama
cadcraft-electrical-mcp

cadcraft-electrical-mcp

device_add

Add one or more electrical devices to a CADCraft project using a catalog ID or device kind, with optional mounting, tags, terminals, and dimensions. Terminal strips also create an empty strip.

Instructions

Add one or more devices. Give catalog_id (see library_search) or at least kind.

Tags are auto-assigned from the profile letter code when omitted (-QA1, -KF2 ... or CR1, M1 in NFPA). Use mount='field' for devices outside the cabinet, 'door' for door-mounted ones. A terminal_strip device also creates its (empty) strip.

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": {
      "items": "<items>"
    },
    "name": "device_add"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemsYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4/5.0
Behavior4/5

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

The annotations already establish that this is a non-read-only, non-destructive, non-idempotent create operation. The description adds useful behavior beyond that: tags are auto-assigned from profile codes when omitted, mount values have specific meaning, and terminal_strip devices create an empty strip. It does not discuss atomicity or duplicate handling, which keeps it below 5.

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

Conciseness5/5

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

The description is front-loaded with the core action, then gives only actionable details about prerequisites, tag defaults, mount semantics, and the terminal_strip side effect. The four sentences are compact, and the parenthetical examples earn their place by clarifying tag behavior.

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?

For a creation tool with annotations and an output schema, the description covers the core invocation conditions and notable side effects. It is not exhaustive about all optional device fields or bulk-operation semantics, but it provides enough context to invoke the tool correctly in common cases.

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

Parameters3/5

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

The description adds meaning for key fields: catalog_id, kind, mount, and tag auto-assignment. However, with reported schema description coverage at 0%, many optional DeviceInput fields such as data, ports, terminals, dimensions, model_dxf, and manufacturer remain unexplained by the description. It partially compensates for the coverage gap but not fully.

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 states a specific verb and resource: 'Add one or more devices', including that the tool accepts a batch via 'one or more'. It points to library_search for catalog lookup, but does not explicitly contrast itself with device_update or device_remove, so sibling differentiation is only implicit.

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 gives a clear prerequisite: provide catalog_id or at least kind, and directs catalog lookup to library_search. It also explains mount values for field/door devices. It lacks explicit when-not guidance or alternatives such as terminals_add, so it stops short of full when/when-not coverage.

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