Skip to main content
Glama
sheares

easyeda-mcp-fix

by sheares

pcb_get_primitives_in_region

Read-onlyIdempotent

Fetch PCB primitives inside a rectangular region defined by left, right, top, and bottom mil coordinates, with options for containment, field projection, and result limits.

Instructions

Get all primitives within a rectangular region on the PCB. 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
topYesTop boundary Y
leftYesLeft boundary X
limitNoTruncate result array to at most N items
rightYesRight boundary X
bottomYesBottom boundary Y
fieldsNoProject results to only these top-level keys. Response includes _availableFields showing all keys. IMPORTANT: Always specify fields when you know what you need — without it, responses include every property and can be extremely large (100KB+), wasting context.
filterNoKeep items matching all conditions (AND). Exact: {key: value}, prefix glob: {key: "R*"}, OR: {key: ["a","b"]}
documentYesTarget document UUID — auto-switches to this document before executing. Get UUIDs from list_instances or editor_get_open_tabs.
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.
leftToRightNotrue=must be fully inside, false=intersecting also counts

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.6.5

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds the coordinate frame (mil, relative to canvas origin, +X right / +Y up), but says nothing about what counts as a 'primitive' in the result, truncation behavior via limit, or response size, which are real behavioral concerns for this tool.

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?

Three tight sentences: purpose first, then the coordinate semantics that most affect correct invocation, then the cross-references. No filler or restatement of the tool name.

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, no-output-schema tool, the description covers the coordinate model and related tools well, and the schema's fields/filter/limit descriptions carry the projection and truncation warnings. It stops short of defining the returned primitive set or the return shape, which the absent output schema leaves partially to inference.

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: the unit (mil, 1 mil = 0.001 inch) and the coordinate frame/orientation for left/right/top/bottom, which the schema only labels as 'Left boundary X' etc. That materially reduces ambiguity about how to supply the boundary values.

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 (get) and resource (primitives) with an explicit scope qualifier ('within a rectangular region'), which is exactly what separates it from pcb_get_all_primitives and pcb_get_primitive_at_point. An agent can pick the right tool without opening a schema.

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?

Usage is implied by the region scope, and it helpfully points to pcb_canvas_origin and pcb_convert_coordinates for coordinate handling. However, it never states when to prefer this over the sibling queries or any preconditions (e.g. requiring a document/instance context, or cost of wide regions).

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