Safety Model
The bridge is designed to be useful before it is powerful.
Default behavior is read-first. Anything that changes the EasyEDA Pro project must be explicit.
Safe by Default
These workflows do not directly change project content:
- live status
- editor context
- component and net search
- schematic snapshots
- pin, net, and component tracing
- connection verification
- navigation
- exports
Use them freely during review and debugging.
Actions That Can Change the Project
Project-changing actions go through:
easyeda_confirmed_actionSupported actions:
saveimportChangesautorouteautolayout
The tool blocks the request unless the confirmation text contains a clear confirmation phrase.
Accepted examples:
I confirmconfirmedconfirma salvarconfirmo
Why Confirmation Exists
AI-assisted exploration often involves guesses, retries, and partial context.
The confirmation gate keeps those exploratory reads separate from actions that can affect the open project.
Confidence Levels
Schematic analysis may return a confidence value:
high: data is strong enough for normal reviewpartial: useful, but some raw EasyEDA data was missing or inferredlow: treat as a hint and verify manually
Always read warnings when they appear.
Practical Rule
For important electrical decisions:
- use the MCP tools to find and explain the issue
- check warnings and confidence
- verify the critical area in EasyEDA Pro
- use confirmed actions only when the intent is clear
Not Implemented
This project does not implement:
- commercial/order operations
- unrestricted editor automation
- offline
.eproparsing