EasyGerber: AI PCB design, layout, and routing

Read generation status

get_generation

Read-onlyIdempotent

Reads stored layout generation status using the same boardRef. Omit generationId to read the active/latest layout job; supply it only to inspect that exact job. Returns generation:null if no layout job exists. While queued or running, wait pollAfterSeconds; stop polling at completed, failed or cancelled. Read get_board for current saved layout and revision after completion. Never call generate_layout to inspect status. Polling does not save private work to an account.

Input Schema

Name	Required	Description	Default
`boardRef`	Yes	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.
`generationId`	No	Layout generation ID returned by generate_layout for this same board. Use the exact job ID when polling or stopping it.

Output Schema

Name	Required	Description	Default
`data`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed11 schema fields changedNov 3, 2026

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",
-  "generationId"
-]New value: +[
+  "boardRef"
+]

addedOutput schema / properties / data / properties / boardRef
```
Added value: +{
+  "type": "string"
+}
```
removedOutput schema / properties / data / properties / generation / additionalProperties
```
Removed value: -{
-  "$ref": "#/$defs/__schema0"
-}
```

addedOutput schema / properties / data / properties / generation / anyOf

Added value: +[
+  {
+    "additionalProperties": {
+      "$ref": "#/$defs/__schema0"
+    },
+    "properties": {
+      "boardId": {
+        "type": "string"
+      },
+      "id": {
+        "type": "string"
+      },
+      "status": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "id",
+      "boardId",
+      "status"
+    ],
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]

removedOutput schema / properties / data / properties / generation / properties

Removed value: -{
-  "boardId": {
-    "type": "string"
-  },
-  "id": {
-    "type": "string"
-  },
-  "status": {
-    "type": "string"
-  }
-}

removedOutput schema / properties / data / properties / generation / required
```
Removed value: -[
-  "id",
-  "boardId",
-  "status"
-]
```
removedOutput schema / properties / data / properties / generation / type
```
Removed value: -"object"
```

changedOutput schema / properties / data / required

Previous value: -[
-  "generation",
-  "boardRevision"
-]New value: +[
+  "generation",
+  "boardRevision",
+  "boardRef"
+]

Changed1 schema field changedNov 3, 2026

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

Changed2 schema fields changedOct 17, 2026

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 / generationId / description

Added value: +"Layout generation ID returned by generate_layout for this same board. Use the exact job ID when polling or stopping it."

First observedOct 17, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive, closed-world), yet the description still adds real behavior: pollAfterSeconds wait cadence, the completed/failed/cancelled stop condition, generation:null when no job exists, and the privacy note that polling does not persist private work. That is substantial value beyond the annotations, though the return shape itself is partly carried by the output schema.

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 purpose, then parameter rule, then return/edge case, then polling lifecycle, then alternatives — a sensible ordering with almost no filler. Slightly dense, and the trailing privacy sentence is mildly tangential, but it still carries information an agent would not otherwise have.

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 two-parameter polling tool with a full output schema and rich annotations, everything the agent needs is present: empty-state behavior, poll cadence, terminal conditions, the handoff to get_board after completion, and sibling exclusions. No meaningful gap remains.

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, but the description adds meaning the schema does not spell out: omitting generationId yields the active/latest job rather than an error, and it must belong to the same boardRef. That is genuine semantic guidance on top of a fully documented schema.

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?

Opens with a specific verb and resource ('Reads stored layout generation status') and pins the scope to the same boardRef. It explicitly distinguishes itself from two siblings, generate_layout and get_board, so an agent can route correctly without opening sibling schemas.

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?

States the exact selection rule for the optional parameter (omit to read active/latest, supply only to inspect that exact job) and gives a terminal-state polling rule. It also names the correct alternative for a different need ('Read get_board for current saved layout and revision after completion') and an explicit do-not-use ('Never call generate_layout to inspect status').

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.