easyeda-mcp-pro

List schematic components

easyeda_schematic_components

Read-onlyIdempotent

Retrieve schematic components with IDs, references, values, footprints, and placement details. Supports focused, page, or all-pages scope for design review and BOM sourcing.

Instructions

List schematic components with IDs, references, values, footprints, placement, and project-instance device IDs. Omitted scope preserves legacy all-pages; focused/all_pages are supported, pageUuid is not. Project-instance device IDs are not valid place_component deviceItem values; use schematic_search_device.

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No
`scope`	No
`offset`	No
`pageUuid`	No
`projectId`	Yes	The project/schematic ID

Output Schema

TableJSON Schema

Name	Required	Description	Default
`error`	No
`total`	Yes
`components`	Yes
`error_code`	No
`error_data`	No
`project_id`	Yes
`read_scope`	No
`not_available`	No
`read_consistency`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed7 schema fields changedv0.19.2Oct 2, 2026

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

addedInput schema / properties / pageUuid

Added value: +{
+  "minLength": 1,
+  "type": "string"
+}

addedInput schema / properties / scope

Added value: +{
+  "enum": [
+    "focused",
+    "page",
+    "all_pages"
+  ],
+  "type": "string"
+}

changedOutput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

addedOutput schema / properties / error_code
```
Added value: +{
+  "type": "string"
+}
```

addedOutput schema / properties / error_data

Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "focusedPageUuid": {
+      "type": "string"
+    },
+    "missingCapability": {
+      "type": "string"
+    },
+    "operation": {
+      "type": "string"
+    },
+    "pageUuid": {
+      "type": "string"
+    },
+    "requestedScope": {
+      "enum": [
+        "focused",
+        "page",
+        "all_pages"
+      ],
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

addedOutput schema / properties / read_scope

Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "focus_changed": {
+      "const": false,
+      "type": "boolean"
+    },
+    "focused_page_uuid": {
+      "type": "string"
+    },
+    "page_uuid": {
+      "type": "string"
+    },
+    "requested": {
+      "enum": [
+        "focused",
+        "page",
+        "all_pages"
+      ],
+      "type": "string"
+    },
+    "resolved": {
+      "enum": [
+        "focused",
+        "page",
+        "all_pages"
+      ],
+      "type": "string"
+    },
+    "source": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "requested",
+    "resolved",
+    "focus_changed",
+    "source"
+  ],
+  "type": "object"
+}

Changed19 schema fields changedv0.19.1Jul 15, 2026

addedInput schema / properties / projectId / description
```
Added value: +"The project/schematic ID"
```
addedOutput schema / properties / components / items / properties / annotated
```
Added value: +{
+  "type": "boolean"
+}
```
addedOutput schema / properties / components / items / properties / bom_eligible
```
Added value: +{
+  "type": "boolean"
+}
```

addedOutput schema / properties / components / items / properties / component_kind

Added value: +{
+  "enum": [
+    "part",
+    "power-symbol",
+    "power-flag",
+    "net-label",
+    "net-port",
+    "sheet-frame",
+    "annotation",
+    "helper",
+    "unknown"
+  ],
+  "type": "string"
+}

addedOutput schema / properties / components / items / properties / deviceLibraryUuid
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / properties / components / items / properties / deviceName
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / properties / components / items / properties / deviceUuid
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / properties / components / items / properties / electrical_eligible
```
Added value: +{
+  "type": "boolean"
+}
```
addedOutput schema / properties / components / items / properties / manufacturerId
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / properties / components / items / properties / primitiveId
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / properties / components / items / properties / raw_footprint
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / properties / components / items / properties / raw_value
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / properties / components / items / properties / rotation
```
Added value: +{
+  "type": "number"
+}
```
addedOutput schema / properties / components / items / properties / symbolName
```
Added value: +{
+  "type": "string"
+}
```

addedOutput schema / properties / components / items / properties / symbol_source

Added value: +{
+  "enum": [
+    "native",
+    "imported",
+    "unknown"
+  ],
+  "type": "string"
+}

addedOutput schema / properties / components / items / properties / x
```
Added value: +{
+  "type": "number"
+}
```
addedOutput schema / properties / components / items / properties / y
```
Added value: +{
+  "type": "number"
+}
```

changedOutput schema / properties / components / items / required

Previous value: -[
-  "reference",
-  "value",
-  "footprint"
-]New value: +[
+  "reference",
+  "value",
+  "footprint",
+  "component_kind",
+  "bom_eligible",
+  "electrical_eligible",
+  "annotated",
+  "symbol_source",
+  "raw_value",
+  "raw_footprint"
+]

addedOutput schema / properties / read_consistency

Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "attempts": {
+      "exclusiveMinimum": 0,
+      "maximum": 9007199254740991,
+      "type": "integer"
+    },
+    "stable": {
+      "type": "boolean"
+    }
+  },
+  "required": [
+    "stable",
+    "attempts"
+  ],
+  "type": "object"
+}

First observedv0.19.0Jul 4, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare readOnly and idempotent, so safety is covered; the description adds non-obvious behavior — that omitting scope silently preserves a legacy all-pages mode — plus the warning that returned project-instance device IDs are not valid place_component deviceItem inputs. That is meaningful disclosure beyond the annotations, though pagination/ordering behavior is unaddressed.

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 dense sentences, front-loaded with the tool's purpose and return payload, followed by the scope caveats and the cross-tool warning. No filler or restated boilerplate.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return-value explanation is optional, yet the description still names the payload fields. Combined with the scope-default and pageUuid caveats, an agent has enough to call this read-only list tool correctly.

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 only 20% (just projectId), so the description must compensate, and it does the most valuable part: it clarifies the scope enum's semantics and flatly states pageUuid is not supported despite appearing in the schema. limit and offset remain undocumented in both places, keeping it below a 5.

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+resource ('List schematic components') and enumerates returned fields (IDs, references, values, footprints, placement, device IDs), which separates it from sibling readers like schematic_nets or schematic_wires. It does not explicitly contrast with the closest sibling, schematic_component_pins, so it stops short of a 5.

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?

It gives real usage context for the scope parameter (omitted = legacy all-pages, focused/all_pages supported) and redirects one case to schematic_search_device when place_component device IDs are needed. However, it never states when to choose this tool over alternatives such as schematic_component_pins or component_pins for detailed per-component work.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server