EasyGerber: AI PCB design, layout, and routing

Search published parts

search_parts

Read-onlyIdempotent

Searches published catalog components. The first candidate includes verified pins when available; other candidates may omit them. Reuse returned IDs, pins and facts; call get_part only when the selected candidate lacks needed pins or facts. Supplied filters apply together; query ranks matching candidates, while factQuery only selects cached facts for those candidates. An optional boardRef applies that board’s strict Part List restriction, when enabled. Check candidates against the requested component type and specifications. If results are unrelated, make at most two retries for that part using a simpler component name or a relevant category from the input schema. Preserve required specifications and explicit restrictions, including any boardRef Part List restriction, on every retry. If no suitable part is found, report that you could not find a suitable part rather than claiming the catalog lacks it.

Input Schema

Name	Required	Description
`limit`	No	Maximum catalog candidates to return, from 1 to 20; defaults to 3.
`query`	No	PCB selection terms: MPN, manufacturer, description or package family. For exact MPNs omit unverified categories unless user-required. Preserve explicit filters and Part Lists; factQuery does not select parts. Required when factQuery is supplied.
`package`	No	Exact catalog label; use query for package families.
`boardRef`	No	Private board reference. For a new board generate 32 random bytes, encode as unpadded base64url, and prepend egbr1_. Keep this same value for creation retries and every later board operation. Copy returned references unchanged. Keep it in this conversation or supported private execution state; never put it in logs or source files. A private board link may carry it in its fragment.
`category`	No	Catalog category.
`factQuery`	No	Cached-fact terms only; requires query. Omit for filter-only searches. It never changes which parts match.
`frequency`	No	Hertz (8e6 = 8 MHz).
`inductance`	No	Exact henries.
`resistance`	No	Exact ohms (10000 = 10 kΩ).
`capacitance`	No	Exact farads (1e-7 = 100 nF).
`jlcpcbBasic`	No	Basic-only when true; otherwise leave unset.
`subcategory`	No	Subcategory, e.g. chip_resistor, mlcc, ldo.
`mountingType`	No	smt: surface mount; tht: through-hole; mixed: both.
`voltageRating`	No	Rated volts.

Output Schema

Name	Required	Description	Default
`data`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedNov 3, 2026

removedInput schema / properties / boardId

Removed value: -{
-  "description": "Optional saved board ID requiring that board’s account or guest access. Enforces its strict Part List when enabled; omit for public catalog browsing.",
-  "format": "uuid",
-  "pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$",
-  "type": "string"
-}

addedInput schema / properties / boardRef

Added value: +{
+  "description": "Private board reference. For a new board generate 32 random bytes, encode as unpadded base64url, and prepend egbr1_. Keep this same value for creation retries and every later board operation. Copy returned references unchanged. Keep it in this conversation or supported private execution state; never put it in logs or source files. A private board link may carry it in its fragment.",
+  "pattern": "^(?:egbr1_[A-Za-z0-9_-]{42}[AEIMQUYcgkosw048]|egba1_[0-9a-f]{8}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{12}\\.[A-Za-z0-9_-]{42}[AEIMQUYcgkosw048])$",
+  "type": "string"
+}

removedInput schema / properties / guestToken

Removed value: -{
-  "description": "Private continuation capability from create_board.guestAccess.guestToken or start_guest_session. Reuse it for this guest board. Never print it or save it in a repository.",
-  "maxLength": 200,
-  "minLength": 32,
-  "type": "string"
-}

addedInput schema / required
```
Added value: +[]
```

Changed2 schema fields changedNov 3, 2026

changedInput schema / properties / boardId / description

Previous value: -"Optional saved board ID. Enforces that board’s strict Part List when enabled; omit to use the full published catalog."New value: +"Optional saved board ID requiring that board’s account or guest access. Enforces its strict Part List when enabled; omit for public catalog browsing."

changedInput schema / properties / guestToken / description

Previous value: -"Private guest-session capability returned by start_guest_session. Never print it or save it in a repository."New value: +"Private continuation capability from create_board.guestAccess.guestToken or start_guest_session. Reuse it for this guest board. Never print it or save it in a repository."

Changed8 schema fields changedNov 1, 2026

changedInput schema / properties / capacitance / description

Previous value: -"Exact capacitance in farads (1e-7 = 100 nF)."New value: +"Exact farads (1e-7 = 100 nF)."

changedInput schema / properties / category / description

Previous value: -"Exact catalog category; omit when unknown."New value: +"Catalog category."

changedInput schema / properties / frequency / description

Previous value: -"Exact frequency in hertz (8e6 = 8 MHz)."New value: +"Hertz (8e6 = 8 MHz)."

changedInput schema / properties / inductance / description

Previous value: -"Exact inductance in henries (1e-6 = 1 µH)."New value: +"Exact henries."

changedInput schema / properties / jlcpcbBasic / description

Previous value: -"Restrict to JLCPCB Basic parts when true; false or omission leaves this filter unset."New value: +"Basic-only when true; otherwise leave unset."

changedInput schema / properties / resistance / description

Previous value: -"Exact resistance in ohms (10000 = 10 kΩ)."New value: +"Exact ohms (10000 = 10 kΩ)."

changedInput schema / properties / subcategory / description

Previous value: -"Exact catalog subcategory, such as chip_resistor, mlcc, or ldo."New value: +"Subcategory, e.g. chip_resistor, mlcc, ldo."

changedInput schema / properties / voltageRating / description

Previous value: -"Exact voltage rating in volts."New value: +"Rated volts."

Changed14 schema fields changedOct 17, 2026

addedInput schema / properties / boardId / description

Added value: +"Optional saved board ID. Enforces that board’s strict Part List when enabled; omit to use the full published catalog."

addedInput schema / properties / capacitance / description

Added value: +"Exact capacitance in farads (1e-7 = 100 nF)."

addedInput schema / properties / category / description

Added value: +"Exact catalog category; omit when unknown."

changedInput schema / properties / factQuery / description

Previous value: -"Cached-fact terms only; requires query. Omit for filter-only searches."New value: +"Cached-fact terms only; requires query. Omit for filter-only searches. It never changes which parts match."

addedInput schema / properties / frequency / description

Added value: +"Exact frequency in hertz (8e6 = 8 MHz)."

addedInput schema / properties / inductance / description

Added value: +"Exact inductance in henries (1e-6 = 1 µH)."

addedInput schema / properties / jlcpcbBasic / description

Added value: +"Restrict to JLCPCB Basic parts when true; false or omission leaves this filter unset."

addedInput schema / properties / limit / description

Added value: +"Maximum catalog candidates to return, from 1 to 20; defaults to 3."

addedInput schema / properties / mountingType / description

Added value: +"smt: surface mount; tht: through-hole; mixed: both."

addedInput schema / properties / package / description

Added value: +"Exact catalog label; use query for package families."

changedInput schema / properties / query / description

Previous value: -"PCB selection terms: MPN, manufacturer, description or package family. For exact MPNs omit unverified categories unless user-required. Preserve explicit filters and Part Lists; factQuery does not select parts."New value: +"PCB selection terms: MPN, manufacturer, description or package family. For exact MPNs omit unverified categories unless user-required. Preserve explicit filters and Part Lists; factQuery does not select parts. Required when factQuery is supplied."

addedInput schema / properties / resistance / description

Added value: +"Exact resistance in ohms (10000 = 10 kΩ)."

addedInput schema / properties / subcategory / description

Added value: +"Exact catalog subcategory, such as chip_resistor, mlcc, or ldo."

addedInput schema / properties / voltageRating / description
```
Added value: +"Exact voltage rating in volts."
```

First observedOct 17, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), and the description adds substantive behavior beyond that: the first candidate carries verified pins while later candidates may omit them, query ranks matching candidates while factQuery only selects cached facts, supplied filters are conjunctive, and an optional boardRef imposes a strict Part List restriction. It also discloses retry limits and the recommended failure-reporting behavior.

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 purpose and the get_part split, then proceeds to filter semantics, retry policy, and failure reporting. It is long for a search tool, but nearly every sentence carries operational instructions; only the 'check candidates against the requested component type' line is somewhat generic advice.

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?

For a 14-parameter search tool with a full output schema, the description covers everything an agent needs that structured fields do not: candidate ordering quality, filter composition, retry bounds, restriction preservation across retries, and how to report a null result. Return-value details are correctly left to the output schema.

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 per-parameter meaning is already documented and the baseline is 3. The description adds cross-parameter semantics the schema states only in fragments: filters apply together, query drives ranking, factQuery never changes which parts match and is only for cached facts, and boardRef applies the board's Part List restriction only when enabled. It does not restate the numeric unit conventions, which the schema already handles.

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 ('Searches published catalog components') and immediately distinguishes itself from the sibling get_part by specifying that get_part is only for candidates lacking needed pins or facts. An agent can identify the tool's role without opening the schema.

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?

Gives explicit routing rules: reuse returned IDs/pins/facts, call get_part only when the selected candidate lacks needed data, retry at most twice with a simpler component name or a category from the schema, preserve required specs and boardRef restrictions on every retry, and report failure rather than asserting the catalog lacks the part. These are when-to-use and when-not-to-use rules plus alternatives, not just context.

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

All EasyGerber: AI PCB design, layout, and routing tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.