Skip to main content
Glama
sheares

easyeda-mcp-fix

by sheares
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

pcb_create_fill

Create a PCB fill region from a polygon on a chosen layer, optionally with a net, then read back the board to report any values EasyEDA did not apply.

Instructions

Create a fill region on the PCB. The result is read back from the board, and notApplied lists any requested value EasyEDA did not keep (EasyEDA Pro 3.2.206 stores every fill as solid with a 0.2 outline width, whatever fillMode and lineWidth say). 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

NameRequiredDescriptionDefault
netNoNet name
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.
fillModeNoFill mode: "solid" (0), "mesh" (1) or "inner_electrical_layer" (2), or the number. Names are converted to the numeric value EasyEDA requires.
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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.6.9
    • addedInput schema / properties / fillMode
      Added value: +{
+  "description": "Fill mode: \"solid\" (0), \"mesh\" (1) or \"inner_electrical_layer\" (2), or the number. Names are converted to the numeric value EasyEDA requires.",
+  "type": [
+    "string",
+    "number"
+  ]
+}
  2. First observedv1.6.5

TDQS

A4/5.0
Behavior5/5

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

It goes well beyond the annotations (readOnly=false, idempotent=false, destructive=false) by disclosing that the result is read back from the board, that notApplied reports requested values EasyEDA rejected, and that EasyEDA Pro 3.2.206 silently stores every fill as solid with a 0.2 outline width regardless of fillMode/lineWidth. That platform-quirk disclosure is exactly the kind of context an agent cannot get from structured fields.

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 behavioral caveats and then coordinate semantics. The coordinate paragraph is dense but every clause (mil units, axis directions, origin relativity) is operationally necessary; there is little 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?

With no output schema, the description correctly compensates by explaining the read-back/notApplied return behavior. Combined with the coordinate conventions and pointer to pcb_canvas_origin/pcb_convert_coordinates, an agent has enough to invoke it correctly; the only real gap is the absence of sibling differentiation among the other create-* PCB tools.

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 description coverage is 100%, so the baseline is 3, but the description adds meaning the schema lacks: polygon and lineWidth coordinates are in mil relative to the canvas origin, with +X rightward and +Y upward. That unit/frame convention is not present in the schema's parameter descriptions, so it earns above baseline.

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 opening sentence gives a specific verb and resource ('Create a fill region on the PCB'), so an agent immediately knows the operation. It does not, however, distinguish itself from closely related siblings such as pcb_create_pour or pcb_create_region, leaving the agent to infer which create-* tool fits.

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?

The description never states when to prefer this tool over pcb_create_pour/pcb_create_region or when-not to use it. It does provide workflow context by naming pcb_canvas_origin and pcb_convert_coordinates as companion tools, which implies the coordinate setup needed before calling, but no 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