Skip to main content
Glama
Sign In

EasyGerber: AI PCB design, layout, and routing

by io.github.EasyGerber
OverviewDiscussionsAdmin

Generate PCB layout

generate_layout
DestructiveIdempotent

Starts one durable layout job for boardRef at expectedRevision and returns generation.id and generation.status without waiting. Use the latest revision from create_board, update_board or get_board. Read status with get_generation using the same boardRef; do not regenerate to inspect progress. Successful completion replaces the saved layout. A requestId supports IDENTICAL retries only; changed arguments need a new requestId. revision_conflict requires get_board; board_busy identifies the existing job to poll. Subject to normal compute capacity and board complexity limits, without AI credits.

Input Schema

NameRequiredDescriptionDefault
boardRefYesPrivate 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.
requestIdYesNew UUID for this operation. Reuse it with identical arguments when retrying an uncertain result; use a new UUID for a different operation.
expectedRevisionYesLatest saved revision from create_board, update_board or get_board. Reuse it if no intervening change is known. A mismatch returns revision_conflict; read the board again before preparing a new operation.

Output Schema

NameRequiredDescriptionDefault
dataYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • removedInput schema / properties / boardId
      Removed value: -{
-  "description": "Saved board ID from list_boards, create_board, claim_guest_board, or an account board URL. Must be accessible to the current account or guest session.",
-  "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"
-}
    • changedInput schema / required
      Previous value: -[
-  "boardId",
-  "expectedRevision",
-  "requestId"
-]New value: +[
+  "expectedRevision",
+  "requestId",
+  "boardRef"
+]
    • addedOutput schema / properties / data / properties / boardRef
      Added value: +{
+  "type": "string"
+}
    • changedOutput schema / properties / data / required
      Previous value: -[
-  "generation",
-  "boardRevision"
-]New value: +[
+  "generation",
+  "boardRevision",
+  "boardRef"
+]
  2. Changed1 schema field changed
    • 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."
  3. Changed1 schema field changed
    • changedInput schema / properties / expectedRevision / description
      Previous value: -"Saved revision returned by get_board. A mismatch returns revision_conflict; read the board again before preparing a new operation."New value: +"Latest saved revision from create_board, update_board or get_board. Reuse it if no intervening change is known. A mismatch returns revision_conflict; read the board again before preparing a new operation."
  4. Changed3 schema fields changed
    • addedInput schema / properties / boardId / description
      Added value: +"Saved board ID from list_boards, create_board, claim_guest_board, or an account board URL. Must be accessible to the current account or guest session."
    • addedInput schema / properties / expectedRevision / description
      Added value: +"Saved revision returned by get_board. A mismatch returns revision_conflict; read the board again before preparing a new operation."
    • addedInput schema / properties / requestId / description
      Added value: +"New UUID for this operation. Reuse it with identical arguments when retrying an uncertain result; use a new UUID for a different operation."
  5. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Beyond the annotations (destructive, idempotent, non-read-only), the description discloses that completion replaces the saved layout, that requestId only supports IDENTICAL retries, and maps error tokens to recovery actions (revision_conflict → get_board; board_busy → poll the existing job). It also notes capacity/complexity limits and that no AI credits are consumed.

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?

It is front-loaded with the action and return shape, then layers retry, polling, and error-recovery rules — nearly every sentence carries an operational constraint. The error-token clause ("revision_conflict requires get_board; board_busy identifies…") is slightly compressed, but nothing is redundant.

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 destructive, asynchronous job tool with an output schema, it covers what an agent needs: preconditions (fresh revision), concurrency/idempotency (requestId semantics), progress-checking (get_generation), and failure recovery. Return-value detail is correctly omitted since an output schema exists.

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 3 is the baseline, but the description adds cross-parameter meaning: expectedRevision must be the newest revision from a sibling call, and requestId's identical-arguments constraint is stated in prose alongside the error outcomes. It stops short of adding format/syntax detail beyond the schema, so it sits just above baseline.

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?

"Starts one durable layout job for boardRef at expectedRevision and returns generation.id and generation.status without waiting" names a specific verb (starts a job), the resource (layout job for a board revision), and the async contract. It is clearly distinguishable from siblings like get_generation and check_board_layout, which read or inspect rather than start work.

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?

It explicitly routes the agent: take the latest revision from create_board/update_board/get_board, and poll with get_generation "using the same boardRef; do not regenerate to inspect progress." That is a direct when-to-use / when-not-to-use rule with a named alternative.

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

Resources