Skip to main content
Glama
Sign In

EasyGerber: AI PCB design, layout, and routing

by io.github.EasyGerber
OverviewDiscussionsAdmin

Stop generation

stop_generation
DestructiveIdempotent

Cancels a queued or running layout generation belonging to the specified board; use get_generation when only checking progress. A completed, failed or already cancelled job retains its terminal status. Cancellation cannot be undone; starting again requires a new job. It can update the saved board revision, so read get_board before further edits. A later job is unaffected.

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.
generationIdYesLayout generation ID returned by generate_layout for this same board. Use the exact job ID when polling or stopping it.

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",
-  "generationId"
-]New value: +[
+  "generationId",
+  "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. Changed2 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 / 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."
  4. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, but the description adds real context beyond them: terminal jobs keep their status (clarifying the idempotent no-op case), cancellation is irreversible, a new job ID is needed to restart, the saved board revision may be mutated by the call, and unrelated later jobs are unaffected. It also flags the side effect on board state that the annotations alone would not reveal.

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 action in the first clause, then alternatives, irreversibility, and side effects in descending priority. Five short clauses are all substantive, though the density of distinct facts in one block makes it slightly harder to scan than a tighter two-sentence version.

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?

An output schema exists and annotations cover the safety profile, so the description only had to carry the behavioural story — which it does, including failure modes (terminal states), irreversibility, and the board-revision side effect. Nothing an agent needs in order to call this correctly appears to be missing.

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% and both parameter descriptions are detailed, so the baseline would be 3. The description adds a cross-parameter constraint not encoded in the schema: the generation must belong to the specified board, meaning the two identifiers are not independently valid. That is a modest but genuine semantic addition.

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 ('Cancels') and resource ('a queued or running layout generation') with explicit scope ('belonging to the specified board'). It also names the sibling it is not — 'use get_generation when only checking progress' — so an agent can separate it from the read-only polling tool without inspecting 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?

Gives an explicit alternative and the condition that selects it ('use get_generation when only checking progress'), plus a follow-up prerequisite ('read get_board before further edits'). It also tells the agent how to resume work after cancellation ('starting again requires a new job'), which is the main post-call decision an agent faces.

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