Skip to main content
Glama
Sign In
EasyEDA Pro MCP

EasyEDA Pro MCP

by VLab-Software
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Run PCB Design Rule Check (DRC)

easyeda_run_drc
Read-only

Runs the native EasyEDA Pro PCB Design Rule Check on the active board and reports detailed violations, categorized counts, evidence, and target details for fixing design errors.

Instructions

Executes the native EasyEDA Pro PCB Design Rule Check (DRC) on the active board and reports detailed violations, categorized counts, evidence, document target, and execution comparison.

Input Schema

NameRequiredDescriptionDefault
ruleNoOptional rule name or code filter (e.g. Clearance, ShortCircuit, UnroutedNet).
limitNoMaximum number of detailed violation records to return.
strictNoEnforce strict design rule checking.
targetNoExpected document target to assert execution on the intended PCB document.
severityNoFilter reported violations by severity level ('all', 'error', or 'warning').
timeoutMsNo
compareWithEditorNoCompare execution results against editor-side DRC error state if available.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv1.4.1
    • 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 / compareWithEditor
      Added value: +{
+  "description": "Compare execution results against editor-side DRC error state if available.",
+  "type": "boolean"
+}
    • addedInput schema / properties / limit
      Added value: +{
+  "description": "Maximum number of detailed violation records to return.",
+  "exclusiveMinimum": 0,
+  "maximum": 500,
+  "type": "integer"
+}
    • addedInput schema / properties / rule
      Added value: +{
+  "description": "Optional rule name or code filter (e.g. Clearance, ShortCircuit, UnroutedNet).",
+  "minLength": 1,
+  "type": "string"
+}
    • addedInput schema / properties / severity
      Added value: +{
+  "description": "Filter reported violations by severity level ('all', 'error', or 'warning').",
+  "enum": [
+    "all",
+    "error",
+    "warning"
+  ],
+  "type": "string"
+}
    • addedInput schema / properties / target
      Added value: +{
+  "description": "Expected document target to assert execution on the intended PCB document.",
+  "properties": {
+    "capturedAt": {
+      "type": "string"
+    },
+    "documentId": {
+      "type": "string"
+    },
+    "documentName": {
+      "type": "string"
+    },
+    "documentType": {
+      "enum": [
+        "schematic",
+        "pcb",
+        "symbol",
+        "footprint",
+        "unknown"
+      ],
+      "type": "string"
+    },
+    "fingerprint": {
+      "type": "string"
+    },
+    "pageId": {
+      "type": "string"
+    },
+    "pageIndex": {
+      "maximum": 9007199254740991,
+      "minimum": -9007199254740991,
+      "type": "integer"
+    },
+    "projectId": {
+      "type": "string"
+    },
+    "projectName": {
+      "type": "string"
+    },
+    "tabId": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}
  2. Addedv1.3.1

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=true, destructiveHint=false), so the lower bar applies. The description does add useful behavioral detail beyond them by enumerating what the run produces — detailed violations, categorized counts, evidence, document target, and execution comparison — which matters because no output schema exists. It omits pass/fail semantics, how the target assertion is enforced, and timeout behavior.

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?

A single front-loaded sentence with the action first and the output inventory trailing. The trailing list is dense but every item describes a real return field, so nothing is filler. Slightly long in the enumerative tail.

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 seven optional parameters, a nested target object, and no output schema, the description compensates by describing the shape of the result. The remaining gap is operational: strict mode, timeoutMs, and target-assertion failure behavior are left entirely to 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 86%, so the schema already documents rule, limit, strict, severity, target, and compareWithEditor. The description only echoes 'document target' and 'execution comparison' at a high level and adds no syntax, defaults, or filtering semantics beyond that. Baseline 3 is appropriate when the schema does the heavy lifting.

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 gives a specific verb ('Executes') and resource ('native EasyEDA Pro PCB Design Rule Check') scoped to 'the active board', which implicitly separates it from easyeda_run_schematic_erc and easyeda_get_drc_rules. It stops short of naming those siblings explicitly, so an agent must infer the boundary rather than read it.

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?

Usage is only implied by the tool name and the mention of an active PCB board; there is no statement of when to run DRC versus fetching rules (easyeda_get_drc_rules) or the DRC edit workflows. No prerequisites, exclusions, or failure conditions are given.

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