Skip to main content
Glama
sheares

easyeda-mcp-fix

by sheares
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

pcb_modify_track

Idempotent

Modify an existing PCB track segment: update start/end coordinates, width, layer, or net in mil units. Use it to fix routing, adjust traces, or reassign nets on the canvas.

Instructions

Modify properties of an existing track segment (line). Coordinates are PCB canvas coordinates in mil (1 mil = 0.001 inch), relative to the canvas origin: +X = rightward, +Y = upward. Lengths (widths, diameters) are also in mil. Use pcb_canvas_origin to read/set the origin offset and pcb_convert_coordinates to convert between canvas and data coordinates.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
netNoNew net name
endXNoNew end X
endYNoNew end Y
layerNoLayer name (e.g. "TopLayer", "BottomLayer", "Inner1".."Inner30", "Multi") or numeric EPCB_LayerId (1=Top, 2=Bottom, 12=Multi). Names are converted to the numeric id EasyEDA requires.
startXNoNew start X
startYNoNew start Y
documentYesTarget document UUID — auto-switches to this document before executing. Get UUIDs from list_instances or editor_get_open_tabs.
lineWidthNoNew track width
instance_idNoTarget EasyEDA instance ID (8-char hex). Required when multiple instances are connected. Omit when only one instance is connected (auto-selected). Use list_instances to see connected instances.
primitiveIdYesThe track primitive ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.6.5

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true, destructiveHint=false, so the safety profile is covered. The description adds the coordinate-space semantics (mil units, +X rightward, +Y upward, origin-relative), which is genuine behavioral context, but it says nothing about failure modes when primitiveId is missing or whether modifications are partial.

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?

Two front-loaded sentences: the action first, then the coordinate conventions and the follow-up tools. Every clause earns its place with no 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?

For a 10-parameter mutation tool with no output schema but full schema coverage and annotations, the description supplies the missing global context (coordinate system, units, origin, conversion helpers). Only edge behavior on invalid primitiveId or partial updates is unaddressed.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds meaning the schema lacks: the units and sign conventions for startX/startY/endX/endY and lineWidth, plus pointers to the origin and conversion tools. That materially helps interpret the geometry parameters.

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?

States a specific verb and resource ('Modify properties of an existing track segment'), which clearly distinguishes it from pcb_create_track and pcb_modify_primitive. It does not explicitly name the sibling tools it is not, but the track-segment scope makes the boundary readable.

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?

There is no explicit when-to-use / when-not-to-use statement versus siblings like pcb_modify_primitive or pcb_create_track. It does implicitly route the agent to pcb_canvas_origin and pcb_convert_coordinates for coordinate handling, which is useful usage guidance but not selection guidance.

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