EasyGerber: AI PCB design, layout, and routing

Permanently delete an account board

delete_board

DestructiveIdempotent

Permanently deletes the specified saved account board when the user requests its removal. Requires explicit boards:delete authorization and personal ownership or organization owner/admin access; guest boards are unsupported. Read get_board first and pass its current revision. Deletion cancels active generation jobs and cannot be undone. A revision conflict requires reading the board again. Missing, already deleted or inaccessible boards return the same not_found error; this does not confirm that an earlier request succeeded. No requestId or replay receipt is supported.

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.
`expectedRevision`	Yes	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.

Output Schema

Name	Required	Description	Default
`data`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedNov 3, 2026

removedInput schema / properties / boardId

Removed value: -{
-  "description": "Saved account board ID from list_boards or get_board. Deletion requires personal ownership or organization owner/admin access.",
-  "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"
+}

changedInput schema / required

Previous value: -[
-  "boardId",
-  "expectedRevision"
-]New value: +[
+  "expectedRevision",
+  "boardRef"
+]

addedOutput schema / properties / data / properties / boardRef
```
Added value: +{
+  "type": "string"
+}
```

changedOutput schema / properties / data / required

Previous value: -[
-  "boardId",
-  "deleted"
-]New value: +[
+  "boardId",
+  "deleted",
+  "boardRef"
+]

Changed1 schema field changedOct 23, 2026

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

AddedOct 17, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Goes well beyond the annotations by disclosing that deletion cancels active generation jobs, is irreversible, and that missing/already-deleted/inaccessible boards all collapse to the same not_found error, which does not confirm an earlier request succeeded. It also states no requestId or replay receipt exists, which is exactly the kind of context destructiveHint alone cannot convey. The only reason it is not a 5 is that the interaction between idempotentHint=true and the not_found-on-replay behavior is implied rather than spelled out.

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-loads the action and condition, then layers authorization, prerequisite read, side effects, and error semantics in a logical order with no filler. It is dense and slightly long, but each clause carries distinct operational information.

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 destructive mutation, everything an agent needs is present: authorization, ownership rules, prerequisite read, side effects, reversibility, and conflict/not_found handling. An output schema exists, so the description is not obliged to explain return values.

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 the baseline is 3, but the description adds operational meaning: expectedRevision should come from get_board and a mismatch yields revision_conflict requiring a re-read. It does not add anything about boardRef beyond the schema, keeping it from a 5.

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 ('Permanently deletes the specified saved account board') plus the triggering condition ('when the user requests its removal'). No sibling tool performs deletion, and the description explicitly points to get_board as the prerequisite read, so an agent can place it precisely among the siblings.

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 preconditions: boards:delete authorization, personal ownership or org owner/admin access, guest boards unsupported, and the requirement to read get_board and pass its current revision. It also handles the failure branch by naming revision_conflict and prescribing a re-read before retrying.

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.