Skip to main content
Glama
cadcraft-electrical-mcp

cadcraft-electrical-mcp

cabinet_plan

Read-onlyIdempotent

Computes back-plate layout without drawing, returning device positions, rail arrangement, fill percentage, and warnings for cabinet design.

Instructions

Compute the back-plate layout without drawing: device positions, rails, fill %, warnings.

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_plan"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds the non-obvious behavioral point that this computes a layout without producing drawing output, which is context the annotations cannot express; it does not discuss performance or state assumptions.

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?

A single front-loaded clause followed by a compact enumeration of outputs; every token earns its place and there is no filler.

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?

With an output schema present, return values need no explanation, and the description correctly avoids duplicating them in depth. The one residual gap is that a zero-parameter tool implicitly operates on ambient state (the current cabinet/project), which the description never confirms.

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

Parameters4/5

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

The tool takes zero parameters, so there is nothing for the description to disambiguate and the baseline of 4 applies. It adds no noise about inputs.

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?

Names a specific verb ('compute') and resource ('back-plate layout') and enumerates the computed artifacts: device positions, rails, fill %, warnings. The phrase 'without drawing' separates it from drawing/placement siblings such as cabinet_place, though it never names one explicitly.

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?

'Without drawing' implies a preview/analysis use case before committing geometry, which is useful implied guidance. However, it never states when to prefer this over cabinet_configure, cabinet_rails, or cabinet_place, and gives no exclusions or preconditions.

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