Skip to main content
Glama
sheares

easyeda-mcp-fix

by sheares
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

sch_get_connectivity

Read-onlyIdempotent

Retrieve compact schematic connectivity data showing which nets connect component pins, with resolved part names. Trace unnamed nets with the depth parameter to reveal indirect connections.

Instructions

Get compact connectivity data: which nets connect which component pins, with resolved part names. Much smaller than sch_get_netlist — use this for connectivity questions. Returns nets (net → pin connections like "U3.2(GND)") and components (designator → part + pin assignments). Auto-generated net names (starting with $) are hidden from the nets section but still appear in component pin assignments. IMPORTANT: $-prefixed nets (like $R11_1, $U3_7) represent real electrical connections — they are unnamed nets where the designer didn't assign a net label. When investigating a component's full circuit context, you MUST look at $-prefixed nets in its pin assignments and trace them to see what else is connected. These often carry critical signals (reset lines, boot pins, enable pins) that would otherwise be invisible. Use the depth parameter (default 2) to automatically trace through $-prefixed nets and discover indirect connections — so by default, you already see one hop through unnamed nets (pull-ups, series resistors, boot/reset circuitry). Pass depth=1 to see only direct connections, or 3–5 to chase longer chains. The response includes a note field reminding you of the depth used.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
netsNoOnly include these nets and components touching them (e.g. ["GND", "VBUS"])
depthNoHow many hops to trace through $-prefixed (unnamed) nets from the specified designators. depth=1 shows only direct connections. depth=2 (default) follows unnamed nets one hop out — finds buttons/pull-ups/regulators connected through series resistors. Higher values chase longer chains. Only used with designators parameter.
refreshNoIf true, bypass the netlist cache and force a fresh recompute. Use after editing the schematic directly in the EasyEDA UI (edits made through these tools invalidate the cache automatically).
documentYesTarget document UUID — auto-switches to this document before executing. Get UUIDs from list_instances or editor_get_open_tabs.
designatorsNoOnly include these components and nets touching them (e.g. ["U3", "U8"])
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.6/5.0
Behavior5/5

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

Annotations already establish the safe-read profile, and the description adds real behavioral context beyond them: netlist caching and when refresh is needed, the hiding of $-prefixed net names, the depth default and its indirect-discovery behavior, and the note field in the response. This is genuinely useful disclosure for correct interpretation of results.

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?

The purpose and the sch_get_netlist comparison are front-loaded, and the depth guidance is actionable. It is on the long side and revisits $-prefixed nets in two places, which is mildly redundant, but most sentences carry distinct information.

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?

With no output schema, the description compensates by describing the return structure (nets and components sections, pin notation like "U3.2(GND)") and the note field. Combined with the caching and net-naming caveats, an agent has everything needed to call and interpret it.

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 the schema already documents all six parameters, including the depth semantics and the nets/designators filters. The description largely restates depth behavior rather than adding syntax or interpretation the schema lacks, so the baseline 3 applies.

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+resource (get connectivity data: nets → component pins) and explicitly contrasts itself with the sibling sch_get_netlist, so an agent can route between them without opening either schema. Scope and output shape are named concretely.

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?

Explicitly says to use this for connectivity questions and that it is much smaller than sch_get_netlist, names the alternative tool, and gives when-to-use guidance for depth (1 vs 2 vs 3–5) and refresh (after editing in the UI). Both primary decision points are covered.

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