Skip to main content
Glama
ProductOfAmerica

mcp-server-kicad

add_copper_zone

Create an unfilled copper zone on a specified layer for a given net. Define polygon corners, clearance, and thermal relief settings for KiCad PCB design.

Instructions

Create an unfilled copper zone. Call fill_zones afterward to compute fills.

Args:
    net_name: Name of the net to assign to this zone (e.g. "GND")
    layer: Copper layer (e.g. "F.Cu", "B.Cu")
    corners: List of {x, y} dicts defining the zone polygon (min 3)
    clearance: Zone clearance in mm
    min_thickness: Minimum copper thickness in mm
    thermal_relief: Use thermal relief pads (True) or solid connection (False)
    thermal_gap: Thermal relief gap in mm
    thermal_bridge_width: Thermal relief bridge width in mm
    priority: Zone fill priority (higher fills first)
    pcb_path: Path to .kicad_pcb file

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
net_nameYes
layerYes
cornersYes
clearanceNo
min_thicknessNo
thermal_reliefNo
thermal_gapNo
thermal_bridge_widthNo
priorityNo
pcb_pathNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
netYes
layerYes
cornersYes
clearance_mmYes
Behavior3/5

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

Annotations provide no special hints (readOnlyHint=false, destructiveHint=false). The description adds the key behavioral detail that the zone is unfilled and requires separate fill computation, but does not disclose other side effects, file modification timing, or error handling. This is adequate but leaves gaps.

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 front-loaded with the main purpose and includes a structured parameter list. It is concise but could benefit from better formatting (e.g., bullet points) to improve readability. No unnecessary sentences.

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?

Given the tool's complexity (10 parameters, chained workflow), the description covers the essential steps: create zone, then call fill_zones. It explains all parameters. The existence of an output schema reduces the need for return value documentation, but some mention of the tool's effect on the PCB file would enhance completeness.

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, making the description the sole source of parameter meaning. It provides clear one-line explanations for all 10 parameters, including examples (e.g., 'GND' for net_name) and structure hints (e.g., corners as list of {x,y} dicts). This adds significant value.

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 name 'add_copper_zone' and description 'Create an unfilled copper zone' clearly state the action and resource. It distinguishes from sibling tools like 'fill_zones' and 'add_keepout_zone' by specifying it creates an unfilled zone and directing to call fill_zones afterward.

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 says 'Call fill_zones afterward to compute fills', guiding the agent on the next step. However, it lacks explicit when-not-to-use or alternative tools like add_keepout_zone, though the name provides some distinction.

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