Skip to main content
Glama
Sign In
wara

wara

by Hercast
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

altium_move_components

Idempotent

Move or rotate up to 50 PCB components using relative or absolute coordinates and optional rotation. Preview changes first; apply writes them in memory for Ctrl+Z undo.

Instructions

Move or rotate components on the open PCB. Per component give either dx_mil/dy_mil (relative) or x_mil/y_mil (absolute, from the board origin), and optionally rotation_deg (absolute, 0 to <360). 1 to 50 components. apply=false (default) only previews and never touches Altium; apply=true writes. Moves stay in memory on the PCB (not saved); Ctrl+Z undoes them.

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": {
      "changes": "<changes>"
    },
    "name": "altium_move_components"
  }
}

Input Schema

NameRequiredDescriptionDefault
applyNo
changesYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare non-read-only but non-destructive behavior; the description goes further and discloses the traits that matter most here: preview-by-default, edits stay in memory and are not saved, Ctrl+Z reverts them, and the batch is capped at 1–50 components. This is exactly the persistence/reversibility context an agent needs before mutating a live board. Note the description's relative-move semantics sit awkwardly with the annotation's idempotentHint=true, but the description itself makes no idempotency claim, so this is an annotation accuracy issue rather than a description contradiction.

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?

Four tight sentences, front-loaded with the action, then positioning modes, then safety semantics. Every clause carries load-bearing information — no restatement of the name or filler.

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 the description covers mode, geometry, limits, and persistence. Missing only edge-case behavior: conflicting coordinate specifications and whether a 50-component batch is applied atomically or partially on error.

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?

Adds meaning the schema does not: mutual exclusivity of dx/dy versus x/y ('give either ... or ...'), that x/y are measured from the board origin, that rotation is absolute 0 to <360, and the 1–50 batch bound. The one residual gap is that it never says what happens if a caller supplies both relative and absolute coordinates, which the schema's anyOf technically permits.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb pair and resource: 'Move or rotate components on the open PCB.' No sibling tool shares this capability (the other siblings are read/inspect/parameter tools), so the boundary is unambiguous from the name plus description alone.

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

Usage Guidelines4/5

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

Explicitly distinguishes the two operating modes: 'apply=false (default) only previews and never touches Altium; apply=true writes,' which tells the agent exactly when to use which. It also routes between relative (dx/dy) and absolute (x/y) positioning. It stops short of naming any alternative tool or stating preconditions such as a PCB document being open, though the phrase 'on the open PCB' implies it.

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

Deploy Server

Other Tools