easyeda-mcp-pro

Capture canvas image

easyeda_canvas_capture

Read-only

Captures the visible EasyEDA schematic or PCB canvas as PNG for a specified tab or the last-focused tab. Downsamples oversized images without cropping and reports original and final dimensions.

Instructions

Capture the visible EasyEDA schematic/PCB canvas as PNG. Captures the given tab or last-focused tab. Oversized PNGs are downsampled without cropping and report original/final dimensions.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`tabId`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`error`	No
`captured`	Yes
`file_name`	No
`mime_type`	No
`byte_length`	No
`downsampled`	No
`image_base64`	No
`not_available`	No
`image_dimensions`	No
`payload_budget_bytes`	No
`original_image_dimensions`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 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 / downsampled
```
Added value: +{
+  "type": "boolean"
+}
```

addedOutput schema / properties / image_dimensions

Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "height": {
+      "exclusiveMinimum": 0,
+      "maximum": 9007199254740991,
+      "type": "integer"
+    },
+    "width": {
+      "exclusiveMinimum": 0,
+      "maximum": 9007199254740991,
+      "type": "integer"
+    }
+  },
+  "required": [
+    "width",
+    "height"
+  ],
+  "type": "object"
+}

addedOutput schema / properties / original_image_dimensions

Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "height": {
+      "exclusiveMinimum": 0,
+      "maximum": 9007199254740991,
+      "type": "integer"
+    },
+    "width": {
+      "exclusiveMinimum": 0,
+      "maximum": 9007199254740991,
+      "type": "integer"
+    }
+  },
+  "required": [
+    "width",
+    "height"
+  ],
+  "type": "object"
+}

addedOutput schema / properties / payload_budget_bytes

Added value: +{
+  "exclusiveMinimum": 0,
+  "maximum": 9007199254740991,
+  "type": "integer"
+}

Addedv0.19.1Jul 15, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and idempotentHint=false; the description adds real behavioral context beyond that: oversized PNGs are downsampled without cropping and original/final dimensions are reported. This is useful, non-obvious behavior for a capture tool.

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?

Two tight sentences with no wasted words; the core action is front-loaded and the downsampling caveat follows immediately.

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 so return values need not be explained, yet the description still notes what gets reported (original/final dimensions). For a single-param capture tool this is nearly complete; only sibling differentiation is missing.

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 coverage is 0% and there is one optional parameter (tabId). The description compensates by explaining that the tab is either the given one or the last-focused tab, which clarifies the optional/default semantics beyond the bare schema.

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+resource: captures the visible EasyEDA schematic/PCB canvas as PNG. This clearly distinguishes it from most siblings, though it does not explicitly contrast with the close sibling easyeda_canvas_capture_region (which implies a sub-region capture).

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?

Provides implied context via 'the given tab or last-focused tab', telling the agent the capture target defaults to the active tab. However, it gives no explicit when-to-use guidance nor routes the agent between this tool and easyeda_canvas_capture_region or easyeda_canvas_locate.

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

Deploy Server