Skip to main content
Glama
sheares

easyeda-mcp-fix

by sheares

sch_get_netlist

Read-onlyIdempotent

Export raw schematic netlist data in a chosen format, like Allegro, PADS, or EasyEDA, for specific netlist exports or full raw dumps.

Instructions

Get the raw schematic netlist in the specified format. WARNING: The JLCEDA format response is very large (100KB+). Prefer sch_get_connectivity for connectivity questions — it returns the same net/pin data in a much more compact format with resolved part names. Only use this tool when you need a specific netlist export format (Allegro, PADS, etc.) or the full raw netlist data.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeNoNetlist format type
limitNoTruncate result array to at most N items
fieldsNoProject results to only these top-level keys. Response includes _availableFields showing all keys. IMPORTANT: Always specify fields when you know what you need — without it, responses include every property and can be extremely large (100KB+), wasting context.
filterNoKeep items matching all conditions (AND). Exact: {key: value}, prefix glob: {key: "R*"}, OR: {key: ["a","b"]}
documentYesTarget document UUID — auto-switches to this document before executing. Get UUIDs from list_instances or editor_get_open_tabs.
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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.6.5

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive behavior, and the description adds real behavioral context not in them: the JLCEDA response can exceed 100KB. It does not, however, disclose truncation/pagination behavior despite a 'limit' parameter existing, so it stops short of full disclosure.

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?

Three sentences, front-loaded with the action, then the warning, then the routing rule. Every sentence earns its place and there is no repetition of schema or annotation content.

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?

For a 6-parameter read tool with no output schema and full schema coverage, the description covers the essential decision (which netlist tool) and the output-size hazard. It is close to complete, though it could say more about what the raw netlist payload contains versus the compact connectivity response.

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

Parameters3/5

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

Schema description coverage is 100%, so every parameter is already documented in the schema, which sets the baseline at 3. The description's mention of formats (Allegro, PADS) only echoes the enum values in the schema rather than adding new semantics.

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?

States a specific verb and resource ('Get the raw schematic netlist') plus the format-scoping ('in the specified format'), and explicitly names the sibling sch_get_connectivity as the thing it is not. An agent can distinguish it from all other sch_* tools without opening a schema.

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

Usage Guidelines5/5

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

Gives an explicit when-not (connectivity questions), a named alternative (sch_get_connectivity) with the reason it is preferred, and the precise condition that selects this tool instead (need for a specific export format such as Allegro/PADS or the full raw netlist). Nothing is left to inference.

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