Skip to main content
Glama
Nivakaran-S

eda-agent

by Nivakaran-S
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

pcb_move_components

Reposition and rotate multiple PCB components in one IPC transaction to apply layout passes or adjust placement sets without repeated single-component moves.

Instructions

Move and/or rotate MANY PCB components in ONE IPC round-trip.

PREFER THIS over moving one component per call. Each singular move is a full LLM turn (5-15 s); one call to this tool repositions every component in the list in a single Altium transaction.

Typical uses: applying a full layout pass, running an auto-placement result, undoing and redoing a placement set, adjusting a row of components relative to each other.

Args: moves: List of move dicts. Each dict supports: designator (required) , target component x (optional) , new X in mils y (optional) , new Y in mils rotation (optional) , new rotation in degrees

Example:
    [
      {"designator": "U1", "x": 5000, "y": 5000, "rotation": 0},
      {"designator": "R1", "x": 5200, "y": 4800},
      {"designator": "C1", "rotation": 90},
    ]

Returns: Dictionary with per-designator results and a count.

Input Schema

NameRequiredDescriptionDefault
movesYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.1

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations, the description carries the burden and adds useful behavioral context: all moves happen in a single Altium transaction and avoid the cost of separate LLM turns. It does not explicitly describe permissions, rollback behavior on partial failure, or validation of invalid designators, so the behavioral profile is not fully complete.

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?

The description is front-loaded with the main action and rationale, then structured into Args, Example, and Returns. Despite being longer than a one-liner, every section helps with a nested parameter tool and there is no notable 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?

The description covers the nested parameter format and notes the return value, and an output schema exists. However, for a mutating batch operation with no annotations, it could be more complete by stating preconditions and what happens when one designator fails or is missing.

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

Parameters5/5

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

The input schema has only a minimally described array with additionalProperties, and schema description coverage is 0%. The description compensates by defining each move object's fields: required designator, optional x/y in mils, and optional rotation in degrees, plus a concrete example.

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?

The description states a specific verb and resource: moving and/or rotating PCB components. It also scopes the operation as batch-oriented ('MANY ... in ONE IPC round-trip') and explicitly contrasts it with singular moves, so an agent can distinguish its role without opening the schema.

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?

It gives clear usage guidance by preferring this tool over moving one component per call and by listing typical batch-use scenarios. It does not explicitly compare against PCB placement/alignment siblings such as pcb_align_components or pcb_place_components, so it stops short of full alternative routing.

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