Skip to main content
Glama
Sign In
KiCad MCP Server

KiCad MCP Server

by brovk2008
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

run_drc

Run a Design Rules Check on a PCB layout to detect violations and generate a report.

Instructions

Run Design Rules Check (DRC) on a PCB layout.

Returns the report and any violations detected.

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": {
      "board_path": "<board_path>"
    },
    "name": "run_drc"
  }
}

Input Schema

NameRequiredDescriptionDefault
severityNowarning
board_pathYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.6/5.0
Behavior2/5

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

Only states it returns a report and violations; no disclosure on side effects, permissions, or performance. Annotations are absent, so the description carries full burden but provides minimal behavioral context.

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?

Two-sentence description is very concise and front-loaded, but lacks structure and could include more details without becoming verbose.

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 2 parameters and no output schema, the description is insufficient. It does not specify severity values, output details, or how violations are structured.

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

Parameters1/5

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

Schema description coverage is 0%, and the description adds no meaning to the two parameters (severity and board_path). Severity's default 'warning' is noted but not explained.

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?

Description clearly states it runs a Design Rules Check on a PCB layout and returns violations. It is specific but does not explicitly distinguish from sibling tools like run_erc or run_kicad_cli.

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?

No guidance on when to use this tool versus alternatives, no prerequisites or exclusions mentioned.

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

Deploy Server

Other Tools