Skip to main content
Glama
cadcraft-electrical-mcp

cadcraft-electrical-mcp

cabinet_place

Place a device manually at specified lower-left plate coordinates in millimeters; omit x and y to restore automatic placement.

Instructions

Place a device manually (lower-left corner, plate coordinates, mm). Omit x/y to return to auto.

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": {
      "tag": "<tag>"
    },
    "name": "cabinet_place"
  }
}

Input Schema

NameRequiredDescriptionDefault
xNo
yNo
tagYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.4/5.0
Behavior4/5

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

Annotations declare mutation (readOnlyHint=false) but non-destructive, so the description is not obligated to re-state safety. It does add useful behavior beyond the annotations: the coordinate origin, the unit (mm), and the fact that omitting coordinates reverts the device to automatic placement. It doesn't cover failure modes (out-of-bounds coordinates, unknown tag) or confirm that re-placing at the same point is stable.

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?

Two sentences, zero padding, with the reset rule front-loaded right after the core action. Brevity is bought partly by leaving terms like "auto" and the tag parameter unexplained.

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?

An output schema exists, so return values need no explanation, and annotations cover the safety profile. Against that, a 3-parameter mutation with 0% schema coverage gets no description of the required tag, no device-existence prerequisite, and no error behavior — enough gaps to matter for correct invocation.

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, and it only half does. It explains x/y semantics well (lower-left origin, mm, null means auto) but never mentions the required `tag` parameter at all, leaving the single mandatory input undefined.

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?

"Place a device manually" gives a specific verb plus resource, and the parenthetical pins down the coordinate convention (lower-left corner origin, plate coordinates, mm). It does not distinguish this from siblings like device_add or device_update, so an agent must infer that this tool positions an existing device rather than creating one.

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?

"Omit x/y to return to auto" is a real usage rule for one branch of behavior, so guidance is not absent. However, there is no statement of when to prefer this over device_add/device_update, no precondition that the tag must already exist, and "auto" is never defined.

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