Skip to main content
Glama
cadcraft-electrical-mcp

cadcraft-electrical-mcp

sheet_move

Moves a schematic sheet to a specified 1-based position while keeping the cover first and terminal or cabinet sheets last.

Instructions

Move a sheet to a 1-based position in the set (cover stays first, terminal/cabinet sheets last).

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": {
      "sheet_id": "<sheet_id>",
      "position": "<position>"
    },
    "name": "sheet_move"
  }
}

Input Schema

NameRequiredDescriptionDefault
positionYes
sheet_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

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?

Annotations already declare this is a non-read-only, non-destructive, non-idempotent mutation. The description adds genuinely new context about ordering invariants (cover stays first, terminal/cabinet sheets last), which hints that the effective position may be adjusted. It does not say whether an out-of-range or conflicting position fails, clamps, or succeeds silently.

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?

A single sentence with the action front-loaded and the ordering caveat in a tight parenthetical. No filler or redundant restatement of the tool name.

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?

For a two-parameter mutation whose safety profile is covered by annotations and whose return values are covered by an output schema, only the ordering/error semantics for 'position' are thin. Nothing critical is missing for a caller with a known sheet_id and target index.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so the description must carry the parameters. It does add real meaning for 'position' (1-based indexing) and notes ordering constraints, but 'sheet_id' is left entirely to the schema and the interaction between a requested position and the fixed cover/last-sheet slots is not spelled out.

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 gives a specific verb plus resource ('Move a sheet') and states the destination semantics ('a 1-based position in the set'). It is clearly distinct from sheet_get/sheet_remove, though it never explicitly contrasts with the closest sibling, sheet_update.

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 explicit statement of when to use this versus sheet_update or sheet_add, and no prerequisites or exclusions. Reordering intent is only implied by the verb 'Move'.

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