Skip to main content
Glama

export_fabrication

Exports JLCPCB-ready Gerbers, drills, pick-and-place and BOM CSVs, board images, and STEP into a project folder and zip; refuses designs with circuit-check errors.

Instructions

Write the JLCPCB fabrication files to -fab/ and a zip: Gerbers, drills, pick-and-place and BOM CSVs, pictures of the board as made and a STEP model. Call it after a clean check_circuit: a design with errors is refused.

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": {
      "file": "<file>"
    },
    "name": "export_fabrication"
  }
}

Input Schema

NameRequiredDescriptionDefault
outNoProject folder to write into, e.g. fab
fileYesCircuit file

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already indicate this is not read-only and not destructive, but the description adds important behavior: it writes a directory and zip, lists the generated artifacts, and discloses the clean-check precondition and refusal on errors. It does not address overwrite behavior for an existing output folder, but the operational profile is otherwise well disclosed.

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?

Two tight sentences: the first states what is produced, the second states the precondition and failure mode. There is no redundant wording or buried information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a fabrication export tool with no output schema, the description is largely complete: it names the output artifacts, output location pattern, and the key precondition. A minor gap is that it does not say what the tool returns or how existing output folders are handled.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the parameters are already documented. The description adds context about the output location pattern (<name>-fab/) and zip, but it does not clarify how the optional out folder interacts with that naming convention or what file exactly should be supplied beyond the schema's 'Circuit file' description.

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?

The description states a specific verb (Write) and resource (JLCPCB fabrication files) and enumerates the exact artifacts produced: Gerbers, drills, pick-and-place, BOM CSVs, board pictures, and STEP. This makes the tool's scope immediately understandable and separates it from simple summary or check tools.

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?

It explicitly says to call this after a clean check_circuit and notes that a design with errors is refused, giving a clear precondition. It does not discuss alternatives such as export_package or bom, but the sequencing guidance is strong.

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