Skip to main content
Glama
cadcraft-electrical-mcp

cadcraft-electrical-mcp

cadcraft_open

Open a generated electrical drawing or cabinet plate DXF in the CADCraft desktop app, launching it when needed. Omit the path to open the last build.

Instructions

Open a file in the CADCraft desktop app (launches cadcraft --control <port> if needed). Without path: which='drawings' (sheet set DXF) or 'cabinet' (1:1 plate DXF) of the last build.

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

Input Schema

NameRequiredDescriptionDefault
pathNo
whichNodrawings

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 declare readOnlyHint=false, openWorldHint=true, idempotentHint=false and destructiveHint=false; the description adds the non-obvious reason behind those flags by noting it spawns the desktop process via `cadcraft --control <port>` if it is not running. It does not describe what happens on failure (missing file, no prior build) or whether an already-open document is replaced.

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?

Two short sentences, front-loaded with the action and followed by the default-path branch. No filler, and the parenthetical about launching is placed exactly where it clarifies the side effect.

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?

An output schema exists, so return values need no explanation, and both parameters are covered by the prose. What is missing is what 'the last build' resolves to and what error surfaces when no build or file exists -- relevant for a tool that mutates desktop app state.

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?

Schema description coverage is 0% and `which` has no enum, so the description carries the burden -- and it does, defining 'drawings' as the sheet-set DXF and 'cabinet' as the 1:1 plate DXF from the last build. The `path` parameter is only implicitly characterized (the file to open, mutually exclusive with `which`), which is the main remaining gap.

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?

States a specific verb and resource: opening a file in the CADCraft desktop app, with the side note that it launches the app if needed. The optional `path` vs `which` split is spelled out, so the agent knows it can open either an arbitrary file or the latest build output. It does not distinguish itself from the similarly named sibling `project_open`, leaving that boundary to inference.

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?

Gives a conditional usage rule -- 'Without `path`' use `which` -- which is genuinely actionable. However, it never says when to prefer this over `project_open` or when not to call it (e.g., before a build exists), so guidance is implied rather than complete.

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