Skip to main content
Glama

create_track

Destructive

Create copper tracks on a PCB by defining a path of points, net, layer, and width. Optionally preview geometry with dry_run before committing changes.

Instructions

Creates a copper track (trace) on the board along a path of 2 or more points. The track is assigned to a specific net and placed on a specific copper layer. Points define the track path in millimeters; each consecutive pair of points becomes a straight track segment. The net must already exist on the board. This creates one undo step: Ctrl+Z reverts all segments created in this call. Use dry_run=true to preview the track geometry without creating it. WARNING: This modifies the board. Creating tracks on a nonexistent net will cause DRC violations.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
layerYesCopper layer to place the track on. Valid values: F.Cu, B.Cu, In1.Cu through In30.Cu.
dry_runNoIf true, compute and report the track geometry without actually creating it. Defaults to false.
net_nameYesName of the net this track belongs to. Case-sensitive. Use list_nets to discover available net names. The track must be on a valid net to pass DRC.
width_mmYesTrack width in millimeters. Must be >= the board's minimum track width (check get_design_rules). Common values: 0.15, 0.2, 0.25, 0.3, 0.5 mm.
points_mmYesPath points in millimeters. Must contain at least 2 points. Each consecutive pair creates one track segment. Y increases toward the bottom of the board.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

Beyond the destructiveHint annotation, the description discloses undo behavior, dry-run preview, and consequences of invalid nets. This significantly enhances transparency and does not contradict annotations.

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?

The description is concise but information-dense, with every sentence contributing (purpose, segment logic, prerequisite, undo, preview, warning). It is well-structured and front-loaded.

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?

Given the tool's complexity, the description covers creation mechanism, constraints, side effects, and preview option. Output schema exists, so detailed return value explanation is unnecessary; the description is complete for safe and correct use.

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%, setting a baseline of 3. The description adds value by explaining that each consecutive point pair becomes a straight segment, which is not fully conveyed by the schema's 'Path points' 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 clearly states a specific action ('Creates a copper track (trace)') and resource (track on a board with path of 2+ points). It distinguishes the tool from siblings like create_via and manage_zone by focusing on track creation and net/layer assignment.

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?

Provides clear context such as net existence requirement, dry_run preview, and DRC warning. It lacks explicit alternative tool recommendations or exclusions, but the usage hints are sufficient for practical invocation.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Amagtoto/pcb-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server