Skip to main content
Glama
sheares

easyeda-mcp-fix

by sheares
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

sch_select_primitives

Idempotent

Select and highlight schematic primitives by component designators, pins, or nets. Each call adds to the current selection; clear by clicking empty space in the editor.

Instructions

Select and highlight primitives in the schematic editor by designators, pins, or nets. Selection is additive — each call adds to the current selection. There is currently no programmatic way to clear the selection; the user must click on empty space in the editor to deselect. Pin format: "U1_1" (designator_pinNumber). Components selects the whole component, pins highlights just the pin, nets highlights the entire wire/net.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
netsNoNet names to select (e.g. ["GND", "VBUS"])
pinsNoPins to select as designator_pinNumber (e.g. ["U3_1", "U3_2"])
documentYesTarget document UUID — auto-switches to this document before executing. Get UUIDs from list_instances or editor_get_open_tabs.
componentsNoComponent designators to select (e.g. ["U3", "U13"])
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.5/5.0
Behavior5/5

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

Discloses the critical behavioral trait beyond annotations: selection is additive and each call accumulates, with no programmatic clear path. It also clarifies the distinct effect of each selection category (whole component vs. single pin vs. entire net/wire). With readOnlyHint=false and idempotentHint=true in annotations, the description explains exactly what kind of state change occurs.

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 the core action, then behavior, then the pin format note. Three tight sentences with no filler. Slightly dense but each sentence earns its place.

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?

No output schema, so the description carries behavior, which it does well for a 5-param selection tool. It omits what happens on an unresolvable designator or whether any acknowledgment is returned, but all call-critical context (document auto-switch is in schema, additive semantics here) is present.

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 coverage is 100%, so baseline is 3, but the description adds real meaning: it gives the pin string format ('U1_1' designator_pinNumber) and explains the semantic difference between components, pins, and nets selection targets. This exceeds the schema, which only documents the string format.

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+scope: 'Select and highlight primitives in the schematic editor by designators, pins, or nets.' An agent immediately knows this is a schematic selection tool, distinct from the PCB-only selection siblings (pcb_select_net, pcb_highlight_net, pcb_clear_selection).

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?

Provides a strong usage caveat absent from structured fields: selection is additive and there is no programmatic way to clear it, so the user must click empty space. This tells the agent to batch a single call rather than loop. It stops short of naming alternatives (sch_get_selected/sch_get_selected_ids for inspection), so it lacks explicit routing.

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