Skip to main content
Glama
sheares

easyeda-mcp-fix

by sheares
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

pcb_create_pour

Create a copper pour region on a PCB for a specified net, layer, and polygon, with optional priority, fill method, and island preservation.

Instructions

Create a copper pour region on the PCB. Two upstream EDA bugs to note: (1) pours reflow using the design-rule snapshot taken when the document was opened, so rules written via the API do not affect reflow until the PCB document is closed and reopened (pro-api-sdk issue #34); reopen before rebuilding pours after rule changes. (2) Rebuilding a pour does not cut internal-plane anti-pads for different-net vias created after plane generation (issue #32); regenerate the plane instead. 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
netYesNet name for the pour
layerYesLayer 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.
polygonYesEither an ergonomic point array [{x, y}, ...] (minimum 3 points; the ring is closed automatically and converted to L-mode), or a raw EasyEDA L-mode source array [x1, y1, "L", x2, y2, ..., x1, y1] — coordinates of the first point, then the "L" token, then the remaining points (closed: last point repeats the first)
documentYesTarget document UUID — auto-switches to this document before executing. Get UUIDs from list_instances or editor_get_open_tabs.
pourNameNoName for the pour region
lineWidthNoLine 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.
pourPriorityNoPour priority (higher = poured first)
preserveSilosNoWhether to preserve copper islands
pourFillMethodNoFill method

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.6.5

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare it is a non-read-only, non-idempotent, non-destructive mutation, so the safety bar is partly covered. The description adds genuinely non-obvious behavior: pours reflow against a stale design-rule snapshot until the PCB is reopened (issue #34) and pour rebuilds miss anti-pads for post-plane vias (issue #32). It does not state whether repeated calls create duplicate pours, which matters given idempotentHint=false.

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?

Purpose is front-loaded in the first sentence, followed by actionable bug caveats and unit conventions. It is somewhat long and splits the unit convention across two sentences (coordinates, then lengths), but every sentence carries information an agent would otherwise have to discover the hard way.

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, the description covers units, coordinate frame, known upstream pitfalls, and the helper tools for origin/conversion. Remaining gaps (no return-value note, no idempotency note) are minor given the fully documented schema and existing annotations.

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 would be 3, but the description adds real semantic value beyond the schema: coordinates are canvas coordinates in mil relative to the canvas origin, +X rightward and +Y upward, and lengths are also in mil. It also points to pcb_convert_coordinates for canvas/data conversion, which the schema does not mention.

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?

"Create a copper pour region on the PCB" gives a specific verb and resource, so the agent knows precisely what operation is performed. However, it never distinguishes this from close siblings like pcb_create_region or pcb_create_fill, which an agent could easily confuse with a pour.

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 or when-not guidance, and the near-siblings (pcb_create_region, pcb_create_fill) are not named as alternatives. It does provide operational guidance (reopen the document before rebuilding pours after rule changes) and routes the agent to pcb_canvas_origin / pcb_convert_coordinates for coordinates, so usage is implied but not delimited.

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