Skip to main content
Glama
cadcraft-electrical-mcp

cadcraft-electrical-mcp

cabinet_configure

Configure enclosure and mounting plate dimensions, wire ducts, clearances, and spare rail length for electrical cabinet layout planning.

Instructions

Configure the enclosure and mounting plate (mm). Defaults: 400x500x250 enclosure, 350x450 plate, 40x60 wire ducts, 10 mm duct clearance, 20 % spare rail length.

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": "cabinet_configure"
  }
}

Input Schema

NameRequiredDescriptionDefault
device_gapNo
duct_depthNo
duct_widthNo
plate_widthNo
spare_ratioNo
door_devicesNo
plate_heightNo
plate_marginNo
duct_clearanceNo
vertical_ductsNo
enclosure_depthNo
enclosure_widthNo
enclosure_heightNo
enclosure_catalog_idNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3/5.0
Behavior2/5

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

The annotations declare a non-read-only, non-idempotent, non-destructive, closed-world operation, but the description never says what gets overwritten when values are re-supplied, whether omitted parameters reset to defaults or keep current values, or whether existing placements are invalidated. For a mutation tool that is not idempotent, that is exactly the behavior an agent needs disclosed and the description says nothing about it.

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?

One sentence, front-loaded with scope and unit, then a compact defaults list. It is dense but never padded; the only inefficiency is that the defaults are listed without their parameter names.

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?

A return type being available via the output schema offsets part of the burden, but for a 14-parameter mutation tool with no schema descriptions the definition leaves over a third of the inputs undefined and omits re-configuration behavior entirely.

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?

With 14 parameters and 0% schema coverage, meaning must come entirely from the description, and most is missing: device_gap, door_devices, plate_margin, vertical_ducts, and enclosure_catalog_id go unmentioned. The dimension triples it does mention (400x500x250 enclosure, 350x450 plate, 40x60 ducts) are not mapped to named parameters, so it is ambiguous which value is height, width, or depth.

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 combination ('Configure the enclosure and mounting plate') and names the unit (mm), which separates it from siblings like cabinet_place or cabinet_rails. It never explicitly names those siblings or draws the boundary, and 'configure' stays a little abstract about what happens to the project.

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 implies setup/initial-dimensioning usage, but gives no explicit guidance on when to call it versus cabinet_plan or cabinet_rails, and no prerequisites such as whether a cabinet must already exist. The defaults make a no-argument call meaningful, which is the only implicit usage cue.

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