easyeda-mcp-pro

List schematic wires

easyeda_schematic_wires

Read-onlyIdempotent

List wire segments with IDs, coordinates, net, color, and style for schematic review; paginate with offset past 50 and use scope to target focused or all pages.

Instructions

List wire segments with primitiveId, coordinates, net, color, and style; paginate past 50 with offset. Explicit focused is supported; page/all_pages fail closed on EasyEDA Pro 3.2.149. primitiveId is required by delete_primitive/modify_primitive.

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
`wires`	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"
+}

Addedv0.19.1Jul 15, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint and idempotentHint, so the safety profile is covered. The description adds real behavioral value beyond them: the 50-item pagination cap, the offset mechanism, and the version-specific fail-closed behavior for page/all_pages scopes. Return format detail is partly covered by the existing output schema.

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?

Three tight semicolon-separated clauses with no filler, and the core purpose plus returned fields are front-loaded. Information density is high and every clause earns its place, though the version-pinned fail-closed note adds prose weight.

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?

Given an output schema exists, return values need not be re-explained, yet the description still summarizes the key fields. Combined with pagination and scope caveats, an agent has enough to call this correctly; only pageUuid semantics remain unstated.

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 only 20%, so the description must compensate, and it does: it explains the limit/offset pagination relationship, which scope value is viable ('focused') and which fail closed, and clarifies the role of primitiveId downstream. Only pageUuid and the explicit limit default of 50 are left to the schema.

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?

The description states a specific verb and resource ('List wire segments') and enumerates the returned fields (primitiveId, coordinates, net, color, style). It is clearly distinguishable from siblings like easyeda_schematic_add_wire and easyeda_schematic_delete_primitive without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives concrete usage context: paginate past 50 with offset, only 'focused' scope works while page/all_pages fail closed on EasyEDA Pro 3.2.149, and the returned primitiveId is the input required by delete_primitive/modify_primitive. That last point is excellent cross-tool routing, though it stops short of naming explicit read-alternative siblings.

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

Deploy Server