Skip to main content
Glama
Sign In
circuit-agent

circuit-agent

by mo9652962-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

export_gerber_bundle

Read-onlyIdempotent

Generate native fabrication-ready Gerber RS-274X + Excellon bundle (Edge_Cuts .gm1, Top/Bottom Copper .gtl/.gbl, Top/Bottom Mask .gts/.gbs, Top Silkscreen .gto, drill .drl) directly from placed modules and netlist, eliminating GUI EDA…

Instructions

Generate native fabrication-ready Gerber RS-274X + Excellon bundle (Edge_Cuts .gm1, Top/Bottom Copper .gtl/.gbl, Top/Bottom Mask .gts/.gbs, Top Silkscreen .gto, drill .drl) directly from placed modules and netlist, eliminating GUI EDA dependency. Copper layers carry real footprint pads and the autorouter's actual track geometry.

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": {
      "modules": "<modules>",
      "netlist": "<netlist>"
    },
    "name": "export_gerber_bundle"
  }
}

Input Schema

NameRequiredDescriptionDefault
modulesYesComponent modules dict (from synthesize_circuit output).
netlistYesNetlist dict with 'connections' (from synthesize_circuit output).
ses_textNoOptional Specctra SES session text from a previous autoroute_pcb call. Overrides 'autoroute' and avoids routing twice.
autorouteNoRun the autorouter first so the copper layers carry real tracks (default: true). Set false to export pads only, i.e. an unrouted board.
board_width_mmNoPCB width in mm (default: 70.0).
board_height_mmNoPCB height in mm (default: 50.0).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.16.0
    • addedInput schema / properties / autoroute
      Added value: +{
+  "default": true,
+  "description": "Run the autorouter first so the copper layers carry real tracks (default: true). Set false to export pads only, i.e. an unrouted board.",
+  "type": "boolean"
+}
    • addedInput schema / properties / ses_text
      Added value: +{
+  "description": "Optional Specctra SES session text from a previous autoroute_pcb call. Overrides 'autoroute' and avoids routing twice.",
+  "type": "string"
+}
  2. Addedv0.3.7

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the safety bar is lower; the description still adds real value by explaining that copper layers carry actual footprint pads and autorouter track geometry, and that the default path runs routing first. It does not disclose how the bundle is delivered (written to disk vs returned inline), which matters for an export tool.

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 sentences, zero filler, front-loaded with the deliverable. The parenthetical layer list is long but earns its place by letting an agent verify completeness of the produced bundle.

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

Completeness3/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 does a good job enumerating the bundle contents in its place. However, it leaves the delivery mechanism (file paths, archive, or inline data) and size/pagination behavior unspecified, which is a meaningful gap given nested-object inputs and a six-parameter surface.

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 all six parameters are documented in structured form and the baseline is 3. The description reinforces the meaning of the autoroute default ('real track geometry') but adds no format, unit, or constraint detail beyond what the schema already states.

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?

Specific verb (Generate) plus a precisely named artifact (native fabrication-ready Gerber RS-274X + Excellon bundle), with the exact layer set and file extensions enumerated. An agent can distinguish this from export_excellon_drill, export_ipc2581, or export_specctra_dsn without opening any schema.

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

Usage Guidelines3/5

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

Usage context is implied rather than stated: 'directly from placed modules and netlist' tells the agent the prerequisites come from synthesize_circuit, and the schema mentions ses_text from a previous autoroute_pcb call. But there is no explicit when-to-use/when-not guidance and no routing to siblings such as export_excellon_drill (drill only) or validate_manufacturing_package.

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

Deploy Server

Other Tools