Skip to main content
Glama

get_drc_violations

Retrieve DRC violations from a KiCad PCB file and optionally filter them by violation type to inspect board design rule issues.

Instructions

Give the DRC violations of a board, with a filter by type.

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": "get_drc_violations"
  }
}

Input Schema

NameRequiredDescriptionDefault
pcb_pathYesThe .kicad_pcb file.
violation_typeNoOptional type of the violations, as the DRC report of KiCad gives it, for example "clearance". Empty: all violations.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. It does not state whether the call is read-only, whether it triggers or requires a prior DRC run, what happens if no report exists, or how the violations are returned (though an output schema exists). For a tool with zero annotation coverage this is a significant gap.

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?

A single front-loaded sentence with no filler; the resource and the filtering behavior come first. Its brevity is efficient, though it borders on under-specified for a tool with no annotations.

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?

The output schema covers return values, so the description need not explain them, and parameters are fully documented in the schema. However, with no annotations and no mention of prerequisites or the relationship to run_drc/export_drc_report, the definition leaves an agent without enough operational context to choose and invoke it confidently.

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 description coverage is 100%, so both parameters (pcb_path, violation_type) are already documented in the schema, including the default and empty-string semantics. The description's 'filter by type' merely restates what the violation_type schema field already explains, adding no new format or syntax detail.

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?

The description names a specific verb and resource: retrieving the DRC (design-rule-check) violations of a board, with the filter behavior stated up front. It does not distinguish itself from siblings such as run_drc, export_drc_report, or get_erc_violations, so an agent cannot rule those out from the description alone.

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 explicit when-to-use guidance and no alternatives named. The phrase 'with a filter by type' hints at one usage pattern, but nothing tells the agent whether a DRC must be run first (run_drc) or whether export_drc_report is the better choice for a full report.

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