Skip to main content
Glama
sheares

easyeda-mcp-fix

by sheares
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

sch_get_all_components

Read-onlyIdempotent

Retrieve all components from an EasyEDA schematic, including designators, positions, rotations, and part data, with filters to inspect, verify, or export board details.

Instructions

Get all components in the schematic with their properties, positions, rotations, designators, etc. To identify what a component is, check: designator (e.g. "R1", "U3"), name (part name/number), manufacturer, manufacturerId (manufacturer part number), supplier, supplierId (supplier part number, e.g. JLCPCB/LCSC number), and footprint. All fields: primitiveId, componentType, designator, name, x, y, rotation, mirror, addIntoBom, addIntoPcb, footprint, manufacturer, manufacturerId, supplier, supplierId, net, otherProperty. otherProperty contains user-defined custom attributes — contents vary per component. Template expressions like ={Manufacturer Part} are automatically resolved to their actual values.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoTruncate result array to at most N items
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"]}
refreshNoIf true, bypass the netlist cache and force a fresh recompute. Use after editing the schematic directly in the EasyEDA UI (edits made through these tools invalidate the cache automatically).
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.
skipNetlistNoIf true, skip netlist resolution. Component pin-net names and ={...} template expressions are NOT resolved, but the call returns immediately. Use this on large projects where netlist retrieval is slow.
componentTypeNoFilter by component type (e.g. "part", "netflag", "netport")
allSchematicPagesNoIf true, get components from all schematic pages instead of just the current page

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.6.5

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and non-destructive behavior, so the safety profile is covered. The description adds genuinely useful context beyond that: that otherProperty varies per component and that ={...} template expressions are auto-resolved to real values, which affects how results must be read.

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?

Front-loaded with the core purpose, then layered detail. The 'To identify what a component is' and 'All fields' lists are long but not wasteful, since there is no output schema to convey the return fields. Structure is sound with only mild verbosity.

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 assumes the burden of describing return fields (designator, name, footprint, supplier, net, otherProperty) and template resolution, which makes it usable. Minor gaps remain around result size/pagination behavior, though limit and fields are covered by the schema.

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

Parameters3/5

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

Schema description coverage is 100%, so all nine parameters are already documented in the schema, and the description adds little param-level meaning (no elaboration on limit, filter, allSchematicPages, or componentType). Baseline 3 is appropriate since the schema does the heavy lifting.

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 (all components in the schematic) and enumerates the returned properties. The scope word 'all' plus the schematic context clearly separates it from the singular sibling sch_get_component and from pcb_get_all_primitives.

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?

No explicit statement of when to use this versus sch_get_component or sch_get_netlist, and no exclusions. The 'get all' framing implies bulk retrieval and the schema carries practical guidance (fields projection, refresh, skipNetlist), but the description itself leaves the agent to infer when this is the right call.

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