easyeda-mcp-pro

Search library device

easyeda_schematic_search_device

Read-onlyIdempotent

Search EasyEDA's library for schematic symbols and devices by keyword. Return minimal results (uuid, name, pin count) when only key identifiers are needed.

Instructions

Search for schematic symbols/devices in the EasyEDA library by keywords. Full results carry the library's complete metadata object per device; pass minimal:true to get back only uuid/libraryUuid/name/pin_count/symbol_type when that is all you need.

Input Schema

TableJSON Schema

Name	Required	Description
`key`	Yes	Search keyword(s), matched against device name/description in the library
`page`	No
`minimal`	No	When true, return only uuid/libraryUuid/name/pin_count/symbol_type per device instead of the full library metadata object — use this when the goal is just picking a deviceItem for place_component, to avoid paying for fields you will not read.
`symbolType`	No
`itemsOfPage`	No
`libraryUuid`	No
`classification`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`error`	No
`total`	Yes
`devices`	Yes
`not_available`	No
`provider_tier`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv0.19.2Oct 2, 2026

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

changedOutput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

Changed6 schema fields changedv0.19.1Jul 15, 2026

addedInput schema / properties / key / description

Added value: +"Search keyword(s), matched against device name/description in the library"

addedInput schema / properties / minimal

Added value: +{
+  "description": "When true, return only uuid/libraryUuid/name/pin_count/symbol_type per device instead of the full library metadata object — use this when the goal is just picking a deviceItem for place_component, to avoid paying for fields you will not read.",
+  "type": "boolean"
+}

addedOutput schema / properties / devices / items / additionalProperties
```
Added value: +{}
```

addedOutput schema / properties / devices / items / properties

Added value: +{
+  "pin_count": {
+    "maximum": 9007199254740991,
+    "minimum": 0,
+    "type": "integer"
+  },
+  "symbol_type": {
+    "type": "string"
+  }
+}

addedOutput schema / properties / devices / items / type
```
Added value: +"object"
```

addedOutput schema / properties / provider_tier

Added value: +{
+  "const": "local_library",
+  "type": "string"
+}

First observedv0.19.0Jul 4, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true, so the safety profile is covered. The description adds that full results carry the library's complete metadata object versus a slimmed set under minimal:true, which is useful payload-weight context, but it says nothing about pagination behavior or limits on a 7-parameter, paged search.

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?

Two sentences, no filler, with the core purpose front-loaded and the minimal:true caveat following. Slightly dense in the second clause but every part earns its place.

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?

Since an output schema exists, return-value explanation is not required, and the minimal:true behavior is covered. But for a 7-parameter search with low schema coverage, the definition leaves too many filtering and paging parameters unexplained for an agent to invoke it confidently across use cases.

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 low (29%), so the description should compensate — and it only meaningfully explains 'minimal' (already documented in the schema) plus the keyword intent behind 'key'. Five parameters (page, symbolType, itemsOfPage, libraryUuid, classification) remain undocumented in both places, so the gap is only partially closed.

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: 'Search for schematic symbols/devices in the EasyEDA library by keywords.' It also implicitly distinguishes itself from the write-side sibling easyeda_schematic_place_component by noting the deviceItem-picking use case, so an agent can tell search from placement.

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

Usage Guidelines3/5

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

The description gives conditional guidance for one path — use minimal:true when the goal is just picking a deviceItem for place_component — which is genuinely useful routing. However, it offers no broader when-to-use/when-not guidance relative to other library or component-listing tools, leaving the general invocation context implied.

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

Deploy Server