Skip to main content
Glama

Add schematic wire

easyeda_schematic_add_wire

Add a wire to connect schematic pins or coordinates. Wires with the same net name automatically merge into one net without labels. Collision protection prevents connecting to foreign nets.

Instructions

Add a wire connecting schematic coordinates/pins — real native connectivity. Same netName connects pins globally: separate stubs sharing one name merge into one net (no label needed). NET_COLLISION guards touched points against a foreign net's wire, pin, or flag/port — not mid-segment crossings.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
colorNo
pointsYes
netNameNo
lineTypeNo
lineWidthNo
confirmWriteYesMust be the literal boolean true (not the string "true") to allow this write.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior4/5

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

Description adds real native connectivity, global net merging, and NET_COLLISION behavior beyond annotations; no contradiction with readOnlyHint or idempotentHint.

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?

Two dense sentences with zero waste, efficiently conveying key behaviors and constraints.

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?

Covers essential connectivity and collision logic, but omits output details and required parameter hints beyond schema; still adequate for the complexity.

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?

Only 17% schema description coverage; description adds meaning to netName and points but doesn't detail color, lineType, lineWidth. Partially compensates.

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 clearly states the tool adds wires, explains net naming and collision detection, and distinguishes from sibling tools like adding components or text.

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 provides context for when to use (connectivity, net merging) but lacks explicit exclusions or alternatives; still clear enough for selection.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/oaslananka/easyeda-mcp-pro'

If you have feedback or need assistance with the MCP directory API, please join our Discord server