easyeda-mcp-pro

Run electrical rule check

easyeda_erc_run

Idempotent

Run electrical rule checks on a focused schematic and add inferred floating-pin counts. Page or all_pages scopes fail closed on EasyEDA Pro 3.2.149; unavailable focus returns not_available.

Instructions

Run native schematic ERC and supplement aggregate counts with inferred_floating_pins. Requires a focused schematic. Explicit focused is supported; page/all_pages fail closed on EasyEDA Pro 3.2.149. Native counts remain authoritative; unavailable focus returns not_available.

Input Schema

Name	Required	Description	Default
`scope`	No
`checks`	No
`pageUuid`	No
`projectId`	Yes

Output Schema

Name	Required	Description	Default
`error`	No
`passed`	Yes
`error_code`	No
`error_data`	No
`project_id`	Yes
`read_scope`	No
`violations`	Yes
`error_count`	Yes
`detail_source`	No
`not_available`	No
`warning_count`	Yes
`total_violations`	Yes
`inferred_floating_pins`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv0.19.3Oct 16, 2026
- removedOutput schema / properties / passed / anyOf
```
Removed value: -[
-  {
-    "type": "boolean"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / passed / type
```
Added value: +[
+  "boolean",
+  "null"
+]
```

Changed10 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
```
Added value: +{
+  "type": "string"
+}
```
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 / passed / anyOf

Added value: +[
+  {
+    "type": "boolean"
+  },
+  {
+    "type": "null"
+  }
+]

removedOutput schema / properties / passed / type
```
Removed value: -"boolean"
```

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

Changed2 schema fields changedv0.19.1Jul 15, 2026

addedOutput schema / properties / detail_source

Added value: +{
+  "enum": [
+    "inferred_partial",
+    "native_aggregate_only"
+  ],
+  "type": "string"
+}

addedOutput schema / properties / inferred_floating_pins

Added value: +{
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "designator": {
+        "type": "string"
+      },
+      "pinNumber": {
+        "type": "string"
+      },
+      "primitiveId": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "primitiveId",
+      "designator",
+      "pinNumber"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}

First observedv0.19.0Jul 4, 2026

TDQS

A3.6/5.0

Behavior4/5

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

With annotations covering idempotency and non-destructiveness, the description adds meaningful behavioral detail: fail-closed behavior on unsupported scopes, native counts remaining authoritative, and a not_available fallback when focus is unavailable. It does not explain why readOnlyHint is false for what reads like a check operation, but that is an annotation oddity rather than a description contradiction.

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?

Four short, front-loaded sentences lead with the purpose and then layer constraints; nothing is padded. It is jargon-dense (inferred_floating_pins, not_available) but each sentence carries distinct information.

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

Completeness3/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 not required, and failure modes are covered. However, the missing relationship to the semantic ERC siblings and the undocumented checks/pageUuid parameters leave real gaps for correct invocation.

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 0% across four parameters, so the description must carry the load. It usefully explains the scope parameter's semantics (focused supported, page/all_pages fail) but says nothing about checks, pageUuid, or projectId, leaving half the parameters undocumented anywhere.

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 description opens with a specific verb+resource ("Run native schematic ERC") and clarifies its distinctive output (supplementing aggregate counts with inferred_floating_pins). It does not, however, differentiate itself from the adjacent easyeda_semantic_erc_validate or easyeda_semantic_erc_auto siblings, leaving the agent to guess which ERC variant to pick.

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?

"Requires a focused schematic" plus the note that page/all_pages fail closed on EasyEDA Pro 3.2.149 is genuinely useful operational guidance about when the tool will succeed. But it never names the alternative ERC tools or states when to prefer this native check over semantic validation, so the when-to-use-vs-alternatives dimension is only implied.

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

Deploy Server