Skip to main content
Glama
cadcraft-electrical-mcp

cadcraft-electrical-mcp

cadcraft_execute

Run any CADCraft engine command in the running desktop app started with --control for escape-hatch actions such as zoom or layer.set. Prefer domain tools for drawing content.

Instructions

Escape hatch: run any CADCraft engine command in the running app (e.g. 'zoom', 'layer.set'). Needs the desktop app started with --control. Prefer the domain tools for drawing content.

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": {
      "command": "<command>"
    },
    "name": "cadcraft_execute"
  }
}

Input Schema

NameRequiredDescriptionDefault
paramsNo
commandYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.4/5.0
Behavior3/5

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

The annotations already declare this is not read-only, is open-world, not idempotent, and not destructive, so the description doesn't need to restate the safety profile. It adds genuinely new context the annotations lack: the dependency on a desktop app launched with --control. It does not disclose what happens on failure, whether commands are queued or immediate, or what the call returns, which matters for an arbitrary-command escape hatch.

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?

Three short sentences, front-loaded with the escape-hatch framing, then the prerequisite, then the alternative. No filler or restated title, and every sentence carries actionable information.

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

Completeness2/5

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

There is no output schema, so the description should explain what a successful command returns and how errors are surfaced, but it says nothing about either. Combined with the undocumented `params` object, an agent cannot confidently construct a non-trivial call from this definition alone.

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 must carry parameter meaning. It partially does for `command` by showing dotted string examples like 'layer.set', but `params` — an open object with additionalProperties and no documented keys — is not mentioned at all, leaving the agent to guess its shape on every non-trivial call.

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 uses a specific verb+resource ('run any CADCraft engine command in the running app') and frames the tool explicitly as an 'Escape hatch', which tells an agent this is the catch-all rather than a domain operation. The concrete examples ('zoom', 'layer.set') anchor what a command looks like. It stops short of 5 because 'any command' leaves the actual command namespace and grammar undefined.

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?

'Prefer the domain tools for drawing content' gives a clear alternative and a condition for choosing it, and 'Needs the desktop app started with --control' states a prerequisite the agent must verify. It doesn't say when this tool is genuinely required (i.e., operations no domain tool covers), so the when-to-use boundary is implied rather than fully drawn.

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