Skip to main content
Glama
sheares

easyeda-mcp-fix

by sheares
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

project_import_file

Destructive

Import project files (.epro) into EasyEDA Pro, replacing an existing project or creating a new one. Supports multiple formats like EasyEDA Pro, Altium, KiCad, EAGLE, PADS, and LTspice.

Instructions

Import a project file (.epro) from a local path into EasyEDA Pro. Can import into an existing project (replacing its contents) or create a new project. A new project is saved to the same team/workspace as the project open in the target window (on the desktop client, the local projects folder); open any project there first. Supports EasyEDA Pro, Altium, KiCad, EAGLE, PADS, and LTspice formats. When importing into an existing project (existingProjectUuid set), a backup of the prior project state is taken automatically and committed to a local git-tracked repo — the returned backup.sha references the pre-import state.

FAST-BATCH WORKFLOW: for making many changes at once, it is much faster to export the document or project (document_save_to_file / project_export_file), edit the raw source on disk, then re-upload (document_load_from_file / project_import_file) than to issue many small per-primitive MCP calls. The document source is newline-delimited JSON arrays; .epro files are ZIP archives of the same. Every destructive upload is auto-backed-up to a local git repo first — the response includes a backup SHA you can use to find the prior state if the edit goes wrong. Upload tools accept validate='off'|'warn'|'strict' (default 'strict') which runs the Zod schema on the new source — see document_validate for standalone validation.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
filePathYesAbsolute path to the .epro file to import
fileTypeNoSource format (default: EasyEDA Pro)
instance_idNoTarget EasyEDA instance ID (8-char hex). Required when multiple instances are connected. Omit when only one instance is connected (auto-selected). Use list_instances to see connected instances.
newProjectNameNoDisplay name for a new project. If omitted, EasyEDA takes it from the file.
existingProjectUuidNoUUID of existing project to import into. If omitted, creates a new project.
newProjectOwnerTeamUuidNoTeam uuid to own a new project. If omitted, the open project's team is used.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.6.5

TDQS

A4.6/5.0
Behavior5/5

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

Goes well beyond the annotations by disclosing the destructive semantics concretely (replace existing project contents), the automatic git-tracked backup with its returned backup.sha, and the validate='off'|'warn'|'strict' (default 'strict') schema-checking behavior. These are exactly the mutation-safety details the destructiveHint annotation cannot convey.

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?

Front-loaded with purpose and modes, then workflow guidance, so the agent gets the essentials first. It is somewhat long and repeats the backup/git-repo point in both the first paragraph and the FAST-BATCH paragraph, which is minor redundancy rather than filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a destructive, six-parameter import tool with no output schema, the description covers target selection, formats supported, backup/return-value behavior, and validation modes. Nothing an agent needs before invoking it 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 description coverage is 100%, so parameters are already documented and the baseline is 3. The description adds semantic value beyond the schema by tying existingProjectUuid to the automatic backup behavior and explaining how new-project ownership/target is chosen, though it is not exhaustive.

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?

Opens with a specific verb+resource ('Import a project file (.epro) from a local path into EasyEDA Pro') and immediately disambiguates the two behavioral modes (replace existing project contents vs. create new). It also names the related tools (document_save_to_file / project_export_file, document_load_from_file) so the agent can place it in the workflow without opening schemas.

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?

It clearly states the fast-batch workflow and the condition that selects it ('for making many changes at once ... much faster ... than many small per-primitive MCP calls'), which routes the agent away from per-primitive tools. It also notes the prerequisite of having a project open in the target window. It does not, however, give explicit conditions for choosing existing-project import vs. new-project creation beyond describing the two modes.

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