Skip to main content
Glama
cadcraft-electrical-mcp

cadcraft-electrical-mcp

device_update

Modify device attributes like tag, location, or manufacturer, and rename tags to automatically update all references across sheets, I/O, network, and cabinet.

Instructions

Change device data. Renaming (new_tag) updates all references (sheets, I/O, network, cabinet).

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

Input Schema

NameRequiredDescriptionDefault
tagYes
dataNo
mountNo
portsNo
new_tagNo
functionNo
locationNo
width_mmNo
height_mmNo
model_dxfNo
descriptionNo
part_numberNo
manufacturerNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already establish that this is a non-read-only, non-destructive, non-idempotent write, so safety profile is covered. The description adds genuinely non-obvious behavior beyond that: renaming via `new_tag` propagates to all references. However, it says nothing about partial-update semantics (only `tag` is required), what happens when `tag` doesn't match a device, or whether omitted fields are left untouched.

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, no filler, with the non-obvious cascading-rename fact placed immediately after the purpose statement. It is tight, but for a 13-parameter mutation tool the extreme brevity leaves real gaps rather than reflecting genuine economy.

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?

An output schema exists, so return values need not be described. But given 13 mostly untyped-by-description parameters and no annotations explaining side effects, the description is too thin: an agent cannot know what most fields accept, which ones are mutually constrained, or whether the operation is all-or-nothing.

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% across 13 parameters, so the description must carry the burden and it does not. Only one parameter (`new_tag`) is explained, and even that is limited to its side effect rather than accepted format; `data`, `mount`, `ports`, `function`, `location`, dimensions, `model_dxf`, `part_number`, `manufacturer`, and `description` are left entirely undefined in both schema and description.

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?

"Change device data" names the resource and the mutation, and the second sentence pins the most distinctive capability (renaming with cascading reference updates across sheets, I/O, network, cabinet). It is distinguishable from device_add/device_remove by implying an existing device is modified, though the verb "change" stays generic and the scope of updatable fields is never stated.

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: nothing says to pick this over device_add for new devices, device_remove for deletion, or project_update/sheet_update for other entity types. The only implicit signal is "Change device data" vs. add/remove siblings, which an agent must infer.

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