Skip to main content
Glama
ProductOfAmerica

mcp-server-kicad

set_trace_width

Modify existing PCB trace widths by net name, layer, or bounding box filters. Provide new width in mm.

Instructions

Change the width of existing traces matching the given filters. At least one filter (net_name, layer, or bounding box) is required.

Args:
    width: New trace width in mm
    net_name: Filter by net name
    layer: Filter by layer name (e.g. "F.Cu", "B.Cu")
    x_min: Left edge of bounding box filter (mm)
    y_min: Top edge of bounding box filter (mm)
    x_max: Right edge of bounding box filter (mm)
    y_max: Bottom edge of bounding box filter (mm)
    pcb_path: Path to .kicad_pcb file

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
widthYes
net_nameNo
layerNo
x_minNo
y_minNo
x_maxNo
y_maxNo
pcb_pathNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
traces_modifiedYes
netYes
new_width_mmYes
Behavior3/5

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

Annotations indicate mutation and non-destructive behavior. The description adds units (mm) but does not disclose side effects like file saving, connectivity impact, or undo behavior. It provides minimal behavioral context beyond the core action.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well-structured with a summary sentence, requirement statement, and parameter list. It is front-loaded but the parameter list is lengthy, making it slightly verbose for an 8-parameter tool.

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?

Given the tool's complexity and presence of an output schema, the description is adequate but not fully complete. It does not mention return value, prerequisites (e.g., open project), or immediacy of effect on the design file.

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?

With 0% schema coverage, the description compensates by listing parameter purposes. However, it lacks details on coordinate system for bounding box, default behavior for pcb_path, and precise filter semantics. Some parameters remain underspecified.

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 the action ('Change the width'), the resource ('existing traces'), and the method ('matching the given filters'). It effectively distinguishes from siblings like 'list_pcb_traces' or 'add_trace'.

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?

The description explicitly requires at least one filter (net_name, layer, or bounding box), providing clear usage guidance. However, it lacks comparison to alternative tools or explanation of when not to use this tool.

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/ProductOfAmerica/mcp-server-kicad'

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