Skip to main content
Glama
ProductOfAmerica

mcp-server-kicad

remove_traces

Destructive

Remove trace segments from a KiCad PCB by filtering with net name, layer, or bounding box. Vias are preserved.

Instructions

Remove trace segments matching the given filters. Does not remove vias. At least one filter (net_name, layer, or bounding box) is required.

Args:
    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
net_nameNo
layerNo
x_minNo
y_minNo
x_maxNo
y_maxNo
pcb_pathNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
traces_removedYes
netYes
layerYes
Behavior4/5

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

The description adds important behavioral context beyond annotations: it states that vias are not removed and that at least one filter is required. Annotations already indicate destructiveHint=true, but the description clarifies the scope of destruction. No contradictions.

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 brief summary followed by an Args list. It is slightly long but each sentence adds value. The front-loaded sentence captures the core functionality, and the list format aids readability.

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 (destructive, filter-based removal), the description is complete. It explains the filtering mechanism, required parameters, and what is not affected. The presence of an output schema reduces the need to describe return values.

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

Parameters5/5

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

The input schema has 0% description coverage, meaning parameters only have titles. The description provides detailed explanations for all 7 parameters, including units (mm for coordinates) and examples (e.g., 'F.Cu'). This fully compensates for the schema's lack of descriptions.

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: remove trace segments matching filters. It specifies what is not removed (vias), which distinguishes it from similar tools like remove_tool. The verb 'remove' and resource 'trace segments' are specific, and the sibling list includes add_trace and remove_dangling_tracks, so the description helps differentiate.

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 explains when to use the tool: to remove trace segments based on filters. It explicitly says that vias are not removed and that at least one filter is required. However, it does not contrast with alternatives like remove_dangling_tracks or provide explicit when-not-to-use scenarios.

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