Skip to main content
Glama
sheares

easyeda-mcp-fix

by sheares

pcb_get_net_primitives

Read-onlyIdempotent

Retrieve all PCB primitives—tracks, pads, vias, and more—for a specified net in an EasyEDA document. Filter by type, fields, or limit results to avoid oversized responses.

Instructions

Get all primitives (tracks, pads, vias, etc.) belonging to a specific net

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
netYesThe net name to query
limitNoTruncate result array to at most N items
typesNoFilter by primitive types (e.g. ["Line", "Via", "Pad"])
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

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered by structured data. The description adds no behavioral context beyond that (no note on result size, truncation via limit, or document auto-switching behavior, all of which live in the schema). Consistent with annotations but adds little.

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?

A single well-formed sentence with the scope qualifier front-loaded. Nothing padded, nothing wasted.

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

Completeness3/5

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

For a 7-parameter read tool with a nested filter object and no output schema, the description is minimally adequate. The rich schema and annotations cover the mechanical details, but the description could have warned about response size or pointed to sibling retrieval modes, which it does not.

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, and the description's only contribution is the example list of primitive types (tracks, pads, vias), which loosely maps to the 'types' filter. Baseline 3 is appropriate when the schema does the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb (Get) and resource (primitives) and scopes it to 'belonging to a specific net', which cleanly separates it from siblings like pcb_get_all_primitives, pcb_get_primitives_in_region, and pcb_get_primitives_by_id. It gives the reader enough to know what comes back, though it never names those alternatives explicitly.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no prerequisites, and no mention of the sibling tools that retrieve primitives by other criteria. The agent must infer from the scope phrase alone that this is the net-scoped variant of the family.

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