Skip to main content
Glama
cadcraft-electrical-mcp

cadcraft-electrical-mcp

cadcraft_status

Read-onlyIdempotent

Check whether CADCraft is installed, report its version, and verify if the desktop app control port is reachable before running electrical documentation workflows.

Instructions

CADCraft installation, version and whether the desktop app control port is reachable.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered. The description adds useful substance beyond that by listing exactly what is inspected (installation, version, port reachability). It does not say whether an unreachable port yields an error or a reported false value, which is the main behavioral gap.

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?

A single short sentence with no filler, and the most important element (what is being checked) is front-loaded. The phrasing is a fragment rather than a complete statement, which is the only structural weakness.

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?

With no parameters, an output schema present, and strong annotations, the description need not explain return values or side effects. What remains missing is invocation framing: when to reach for this status check versus the action tools, which matters for a diagnostic endpoint whose result drives the next call.

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 the baseline is 4; there is no argument semantics left for the description to carry. Nothing in the text misdescribes the empty argument object.

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 names the specific resource it reports on: CADCraft installation, version, and whether the desktop app control port is reachable. That is concrete enough to separate it from action siblings like cadcraft_execute or cadcraft_open. It stops short of a 5 because it is a noun-phrase fragment with no verb, so the agent must infer that the tool retrieves/reports rather than configures anything.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance and no alternative is named; the agent must infer that this is a pre-flight/diagnostic check. Nothing states whether to call it before cadcraft_execute or cadcraft_open, or what to do when the port check fails.

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