Skip to main content
Glama
Sign In
circuit-agent

circuit-agent

by mo9652962-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

export_manufacturing_cpl

Read-onlyIdempotent

Generate the JLCPCB SMT pick-and-place (CPL/pos) file with designator, centre X/Y in mm, layer and rotation. Required alongside the BOM for assembly: a part in the BOM but absent here is purchased and never soldered.

Instructions

Generate the JLCPCB SMT pick-and-place (CPL/pos) file with designator, centre X/Y in mm, layer and rotation. Required alongside the BOM for assembly: a part in the BOM but absent here is purchased and never soldered.

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

Input Schema

NameRequiredDescriptionDefault
netlistYesHardware netlist dictionary or synthesis result.
default_layerNoLayer to assign when the netlist does not specify one (default 'Top').Top

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.16.0

TDQS

A4.2/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 low, and the description adds genuinely useful context beyond them: the omission consequence ('a part in the BOM but absent here is purchased and never soldered'). It does not cover the return shape (file text vs. path) or whether it writes to disk, which is the remaining behavioral gap 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, both load-bearing: the first defines the artifact and its contents, the second supplies the cautionary rationale. Nothing is repeated from the title or schema and the framing is front-loaded.

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?

There is no output schema, and the description makes clear what the file contains, which covers most of what an agent needs. It is slightly incomplete in not stating the return form (file content, path, or confirmation), and not clarifying whether the required netlist must already be validated or synthesized.

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 description coverage is 100%, so both 'netlist' and 'default_layer' are already documented in the schema; the description adds nothing about parameter semantics. Baseline 3 is appropriate, though a note on how netlist layer data overrides default_layer would have earned a 4.

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 + resource + output artifact: 'Generate the JLCPCB SMT pick-and-place (CPL/pos) file', and it enumerates the columns produced (designator, centre X/Y in mm, layer, rotation). This distinguishes it from the closely related sibling export_openpnp_job (OpenPnP format) and from export_manufacturing_bom, which it explicitly pairs with.

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?

States the usage context clearly: 'Required alongside the BOM for assembly', which tells the agent this is a second half of a two-file package. It does not explicitly name the alternative format tool (export_openpnp_job) or state when the agent should prefer it, so selection between pick-and-place exporters is left partly to inference.

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