EasyGerber: AI PCB design, layout, and routing

Get part and pins

get_part

Read-onlyIdempotent

Returns a published catalog part and verified pins. Skip this call when search_parts already supplied the needed pins and facts. Use the selected catalog result’s id; returned pins[].number is the padId used in board connections. Use search_parts to find alternatives. factQuery and factOffset select or page cached datasheet facts. An optional boardRef applies that board’s strict Part List restriction, when enabled.

Input Schema

Name	Required	Description
`id`	Yes	Catalog ID returned by search_parts.
`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.
`factQuery`	No	Terms for relevant facts omitted from the supplied bundle.
`factOffset`	No	Continue at nextFactOffset with the same factQuery.

Output Schema

Name	Required	Description	Default
`data`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 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"
-}

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."

Changed3 schema fields changedNov 1, 2026

changedInput schema / properties / factOffset / description

Previous value: -"Zero-based fact offset; defaults to 0. Continue with datasheetFacts.nextFactOffset and the same factQuery."New value: +"Continue at nextFactOffset with the same factQuery."

changedInput schema / properties / factQuery / description

Previous value: -"Terms selecting relevant cached datasheet facts for this part; omit for the default fact bundle."New value: +"Terms for relevant facts omitted from the supplied bundle."

changedInput schema / properties / id / description

Previous value: -"Exact published catalog ID returned by search_parts."New value: +"Catalog ID returned by search_parts."

Changed4 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 / factOffset / description

Added value: +"Zero-based fact offset; defaults to 0. Continue with datasheetFacts.nextFactOffset and the same factQuery."

addedInput schema / properties / factQuery / description

Added value: +"Terms selecting relevant cached datasheet facts for this part; omit for the default fact bundle."

addedInput schema / properties / id / description

Added value: +"Exact published catalog ID returned by search_parts."

First observedOct 17, 2026

TDQS

A4.4/5.0

Behavior3/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), so the bar is lower. The description still adds real operational context: factQuery/factOffset page cached datasheet facts via nextFactOffset, and boardRef conditionally enforces a strict Part List restriction. It does not describe failure modes for an unknown id or what happens when the board restriction blocks the part, which keeps it at a solid 3 rather than higher.

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?

Five tight sentences, front-loaded with the return value, then the skip condition, then id provenance, then paging, then the optional restriction. No filler or restated title.

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?

With an output schema present, return-value detail is not required, and the description still contributes the padId mapping and paging continuation protocol. Remaining gaps are minor: no guidance on error behavior for a stale or invalid id, or on requesting a full fresh bundle instead of a factQuery.

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; the description earns above that by explaining behavior the schema cannot: factOffset continues 'at nextFactOffset with the same factQuery' and boardRef 'applies that board's strict Part List restriction, when enabled.' It also clarifies that the required id comes from search_parts and that pins[].number maps to padId in board connections.

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 ('Returns a published catalog part and verified pins') and immediately contrasts itself with the sibling search_parts. An agent can distinguish lookup-by-id from discovery without opening either 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 an explicit when-not ('Skip this call when search_parts already supplied the needed pins and facts'), a named alternative ('Use search_parts to find alternatives'), and the source of the required id ('the selected catalog result's id'). Selection logic is fully spelled out.

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.