easyeda-mcp-pro

Begin project transaction

easyeda_project_begin_transaction

Open an in-memory, document-scoped transaction for snapshot-backed schematic writes, requiring a transaction ID for participating tools and allowing one active transaction per document.

Instructions

Open an in-memory, document-scoped transaction for snapshot-backed schematic writes. Only tools passed transactionId participate; standalone schematic writes are not auto-captured. Only one active transaction is allowed per document. Beginning a transaction does not modify EasyEDA.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`label`	No
`projectId`	Yes
`ttlSeconds`	No
`maxOperations`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`error`	No
`details`	No
`success`	Yes
`error_code`	No
`transaction`	No
`failed_operation_ids`	No
`restored_operation_ids`	No

Schema Changelog

Changes observed during successful MCP inspections.

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

removedOutput schema / properties / transaction / properties / operations / items / properties / target_type / const
```
Removed value: -"schematic-primitive"
```
addedOutput schema / properties / transaction / properties / operations / items / properties / target_type / enum
```
Added value: +[
+  "schematic-primitive",
+  "pcb-primitive"
+]
```

Addedv0.19.1Jul 15, 2026

TDQS

A4.2/5.0

Behavior5/5

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

Annotations establish that this is not read-only, not idempotent, and not destructive, while the description adds substantive context: the transaction is in-memory, document-scoped, snapshot-backed, only one may be active per document, and beginning one does not modify EasyEDA. These details go well beyond the annotations and are crucial for correct use.

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?

The description is four tight sentences with no waste. Scope and key constraints are front-loaded, and the final sentence clarifies a common misconception about modification.

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 described. However, for a transaction tool with lifecycle parameters like ttlSeconds and maxOperations, the description omits how those affect the transaction, which is important for correct invocation.

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%, so the description must carry the burden for all four parameters. It mentions document scope, implying projectId, but says nothing about label, ttlSeconds, or maxOperations, leaving their behavior and defaults entirely to the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource: 'Open an in-memory, document-scoped transaction for snapshot-backed schematic writes.' It also distinguishes this from standalone schematic writes, which are not auto-captured. An agent can identify the tool's purpose without opening the schema.

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

Usage Guidelines4/5

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

The description gives clear usage context: only tools passed transactionId participate, standalone writes are not captured, and only one active transaction is allowed per document. It does not explicitly name commit/rollback alternatives or state when not to begin a transaction, but the surrounding transactional workflow is clear.

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

Deploy Server