easyeda-mcp-pro

Get rule check summary

easyeda_rule_check_summary

Read-onlyIdempotent

Summarize all design and electrical rule check results for a project to quickly identify issues.

Instructions

Get a summary of all design and electrical rule check results for the project.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`projectId`	Yes

Output Schema

TableJSON Schema

Name	Required	Description	Default
`drc`	Yes
`erc`	Yes
`error`	No
`project_id`	Yes
`not_available`	No
`overall_passed`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed13 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"

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 / drc / properties / error
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / properties / drc / properties / not_available
```
Added value: +{
+  "type": "boolean"
+}
```

addedOutput schema / properties / drc / properties / passed / anyOf

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

removedOutput schema / properties / drc / properties / passed / type
```
Removed value: -"boolean"
```
addedOutput schema / properties / erc / properties / error
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / properties / erc / properties / not_available
```
Added value: +{
+  "type": "boolean"
+}
```

addedOutput schema / properties / erc / properties / passed / anyOf

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

removedOutput schema / properties / erc / properties / passed / type
```
Removed value: -"boolean"
```
addedOutput schema / properties / error
```
Added value: +{
+  "type": "string"
+}
```

addedOutput schema / properties / overall_passed / anyOf

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

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

First observedv0.19.0Jul 4, 2026

TDQS

B3.4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true, so the safety profile is covered. The description adds that the result aggregates ALL design and electrical checks for the project (not a single rule or net), which is useful scoping context, but it discloses nothing about freshness, caching, or result structure.

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?

A single, front-loaded sentence with no filler; every word carries scope information.

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?

An output schema exists and annotations cover the safety profile, so the description needn't explain return values. For a single-parameter read tool, this is nearly complete; only the relationship to the drc_run/erc_run siblings is missing.

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% for the single projectId parameter. The description's phrase 'for the project' implicitly ties projectId to the target project's scope, but adds no format, type, or example beyond that minimal hint.

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 ('Get') and resource ('a summary of all design and electrical rule check results') scoped to the project. However, it does not distinguish itself from siblings like easyeda_drc_run / easyeda_erc_run, leaving the agent to infer whether this aggregate read differs from running the checks themselves.

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

Usage Guidelines2/5

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

No guidance about when to call this versus easyeda_drc_run, easyeda_erc_run, or easyeda_pcb_constraint_report, and no prerequisites or exclusions are stated. Usage is only implied by the tool name and description.

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

Deploy Server