easyeda-mcp-pro

Get board stackup

easyeda_board_stackup

Read-onlyIdempotent

Retrieve PCB layer stackup details—thickness, material, and dielectric constants—from an EasyEDA Pro project for design review and manufacturing.

Instructions

Get the PCB layer stackup including thickness, material, and dielectric constants.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`projectId`	Yes

Output Schema

TableJSON Schema

Name	Required	Description	Default
`error`	No
`layers`	Yes
`project_id`	Yes
`data_source`	No
`total_layers`	Yes
`not_available`	No
`board_thickness_mm`	No

Schema Changelog

Changes observed during successful MCP inspections.

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

Changed2 schema fields changedv0.19.1Jul 15, 2026

addedOutput schema / properties / data_source

Added value: +{
+  "enum": [
+    "physical_stackup",
+    "copper_layer_count_only"
+  ],
+  "type": "string"
+}

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

First observedv0.19.0Jul 4, 2026

TDQS

B3/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 the payload contents (thickness, material, dielectric constants), a small but genuine addition; it says nothing about scoping or failure 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?

One compact sentence, front-loaded with the verb and resource, with no filler. Efficient, though it could have spent a clause on the projectId requirement.

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 values need not be spelled out, and the annotations cover the read-only nature. However, the required projectId is left completely unexplained, which for a one-parameter tool is the main thing an agent needs in order to call it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%: projectId is typed only as a plain string with no description, and the tool description never explains what projectId refers to, its format, or how to obtain it. For the sole required parameter this is a real gap the description should have closed.

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 (PCB layer stackup) and enumerates the returned content (thickness, material, dielectric constants), which separates it from the nearby easyeda_board_layers sibling. It is clear but never explicitly distinguishes itself from that sibling.

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 statement of when to use this tool versus easyeda_board_layers, easyeda_board_dimensions, or easyeda_board_features, nor any prerequisites. The agent must infer the context entirely.

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

Deploy Server