Skip to main content
Glama
ProductOfAmerica

mcp-server-kicad

add_keepout_zone

Define a polygon keep-out zone to restrict tracks, vias, pads, copper pour, and footprints on selected PCB layers.

Instructions

Create a keep-out zone that restricts placement of specified items.

Args:
    corners: List of {x, y} dicts defining the zone polygon (min 3)
    layers: Layers to apply keep-out to (default: ["F.Cu", "B.Cu"])
    no_tracks: Restrict tracks in this zone
    no_vias: Restrict vias in this zone
    no_pads: Restrict pads in this zone
    no_copper_pour: Restrict copper pour in this zone
    no_footprints: Restrict footprints in this zone
    pcb_path: Path to .kicad_pcb file

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cornersYes
layersNo
no_tracksNo
no_viasNo
no_padsNo
no_copper_pourNo
no_footprintsNo
pcb_pathNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
cornersYes
layersYes
restrictionsYes
Behavior2/5

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

Annotations are all false and the description does not disclose any behavioral traits beyond the basic creation action. It fails to mention side effects like permanent file modification, required permissions, or constraints on zone overlap, leaving the agent unaware of important implications.

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 concise with a single sentence plus parameter list. It is front-loaded with the purpose, though the parameter list could be better integrated. No unnecessary words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool has 8 parameters and an output schema, the description lacks contextual completeness. It does not explain the return value (despite output schema existing), prerequisites (e.g., existing PCB file), or behavior under various conditions (e.g., overlapping zones).

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?

Schema coverage is 0%, so the description must compensate. It provides brief explanations for each parameter (e.g., corners as 'List of {x, y} dicts defining the zone polygon (min 3)') which adds basic meaning, but does not go into depth about formats, units, or edge cases.

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 ('Create a keep-out zone') and the resource ('placement of specified items'). This distinguishes it from siblings like 'add_copper_zone' which creates copper pours instead of keep-out zones.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description does not explicitly state when to use this tool versus alternatives or when not to use it. It implies usage when a keep-out zone is needed, but lacks exclusion criteria or comparisons to sibling tools such as 'add_copper_zone'.

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