Skip to main content
Glama
ProductOfAmerica

mcp-server-kicad

set_net_class

Assign nets to a net class and define design rules—track width, clearance, via size, and via drill—by editing the KiCad project file directly, without requiring pcbnew.

Instructions

Create or update a net class with design rules and assign nets.

Edits the KiCad project file (.kicad_pro) alongside the board to
define the net class and assign nets.  Does NOT require pcbnew.

Args:
    name: Net class name (e.g. "Power", "HighSpeed")
    nets: List of net names to assign to this class
    track_width: Track width in mm (None = use default)
    clearance: Clearance in mm (None = use default)
    via_size: Via diameter in mm (None = use default)
    via_drill: Via drill in mm (None = use default)
    pcb_path: Path to .kicad_pcb file. Optional; omit to use the configured default.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYes
netsYes
pcb_pathNo
via_sizeNo
clearanceNo
via_drillNo
track_widthNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
net_classYes
clearance_mmYes
nets_assignedYes
track_width_mmYes
Behavior5/5

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

The description discloses that it edits the .kicad_pro project file alongside the board, a key side effect, and explicitly states that pcbnew is not required. It also explains that None parameters use defaults. These details add significant context beyond the sparse 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 a well-organized docstring that front-loads purpose, then provides behavior and an Args breakdown. Every sentence earns its place with no filler.

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?

The description covers purpose, behavior, file modifications, prerequisites (no pcbnew), and all parameters. Since an output schema exists, return values are already covered. This is complete for a tool with moderate complexity.

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?

Schema coverage is 0%, so the description carries the full burden. The Args section explains all 7 parameters, including units (mm), the meaning of None (use default), and the pcb_path default behavior. This adds clear semantic meaning beyond the schema.

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 begins with 'Create or update a net class with design rules and assign nets,' which clearly states the verb and resource. It uniquely identifies the tool's purpose among siblings by focusing on net class management, which no other sibling tool handles.

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 gives clear context for when to use the tool (to create/update net classes and assign nets) and notes that pcbnew is not required, which is a practical guideline. However, it does not explicitly mention alternatives or when not to use, so it falls short of a full 5.

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