Skip to main content
Glama
Sign In

PCBEditor

by com.pcbeditor
OverviewDiscussionsAdmin

Export manufacturing files

export_board

Exports the board for manufacture as one zip: Gerber X2, Excellon drill, BOM and pick-and-place by default; also IPC-356, IPC-2581, ODB++, assembly and fabrication PDFs, STEP 3D, or a KiCad project. Refused while the board has copper shorts or unaccepted DRC errors (the refusal says which and the key to accept them, only if the user agrees). Returns a download link valid 15 minutes.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "design_id": "<design_id>"
    },
    "name": "export_board"
  }
}

Input Schema

NameRequiredDescriptionDefault
formatsNoFormats (default GERBER_X2, EXCELLON, BOM, CPL).
design_idYesThe design to export.
drc_errors_keyNoThe key from the refusal that names the errors the user accepted.
accept_drc_errorsNoThe DRC error count the user accepted (from a refusal).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Goes well beyond the annotations: discloses the refusal path for shorts/DRC errors, that the refusal names the offending errors and the acceptance key, that acceptance requires user agreement, and that the returned download link expires in 15 minutes. These are exactly the behaviors an agent needs to handle the tool's failure and success modes.

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?

Three sentences, front-loaded with the primary output, then optional formats, then refusal rules and return validity. Every clause carries operational information; nothing is filler.

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?

No output schema exists, and the description compensates by describing the return value (download link, 15-minute validity). Combined with the refusal behavior and format defaults, an agent has everything needed to invoke and handle this tool correctly.

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 real value by explaining the default format set and, crucially, the workflow semantics of drc_errors_key and accept_drc_errors (they come from a prior refusal and represent user-accepted errors). The only gap is not naming parameter identifiers directly.

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 (exports) and resource (the board for manufacture), and enumerates exactly what the zip contains (Gerber X2, Excellon, BOM, CPL, plus optional formats). No sibling tool in the list does export, so the scope is unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explains defaults (Gerber/Excellon/BOM/CPL) and the alternative formats available, and clearly states the refusal condition (copper shorts or unaccepted DRC errors). Lacks an explicit 'use this instead of X' statement, but with no sibling overlap that gap is minor.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All PCBEditor toolsInspect
Try in Browser
Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources