Skip to main content
Glama

run_drc

Run KiCad DRC on a board to check design rules with project severities, and verify schematic-to-board parity when a matching schematic sits beside the board file.

Instructions

Run the DRC of kicad-cli on a board.

The tool uses the severities of the project. When the schematic of the board name is next to the board, the DRC also checks the parity of the schematic and the board.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "pcb_path": "<pcb_path>"
    },
    "name": "run_drc"
  }
}

Input Schema

NameRequiredDescriptionDefault
pcb_pathYesThe .kicad_pcb file.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the disclosure burden. It does add real value by stating that project severities are applied and that schematic/board parity is checked when a matching schematic sits beside the board — non-obvious behavior. However, it is silent on prerequisites (kicad-cli availability), runtime, and whether a run that finds violations is treated as an error.

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?

Three short sentences with the core action front-loaded and no filler. The awkward line break and the slightly loose phrasing ('the schematic of the board name') cost a point but nothing is redundant.

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?

For a single-parameter tool with an output schema, the essentials are covered and return values needn't be explained. The gaps are the absence of annotations combined with no mention of external-CLI prerequisites or side effects, which leaves an agent under-informed about what a DRC run requires.

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?

There is one parameter and the schema covers it fully (pcb_path: 'The .kicad_pcb file.'), so the schema already defines the input. The description does not add path-format, relative-vs-absolute, or resolution details beyond the schema; baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: runs kicad-cli's DRC on a board file. The distinction from run_erc is inferable (DRC on a PCB vs ERC on a schematic), but the description never names siblings or states the boundary explicitly, leaving that step to the reader.

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

Usage Guidelines2/5

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

There is no when-to-use guidance: nothing says whether to call this versus get_drc_violations or export_drc_report, or whether this is the right entry point before exporting a report. The only contextual condition given is about the schematic-parity check, which is behavioral rather than a routing instruction.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.