Skip to main content
Glama

run_erc

Run KiCad ERC on a schematic using project severities and add annotation checks for unannotated symbols, duplicate references, and inconsistent unit values.

Instructions

Run the ERC of kicad-cli on a schematic, with the annotation check of the ERC dialog.

The tool uses the severities of the project. It also runs the annotation check of the ERC dialog of KiCad (symbols that are not annotated, duplicate references, units with different values), which kicad-cli does not run.

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": {
      "schematic_path": "<schematic_path>"
    },
    "name": "run_erc"
  }
}

Input Schema

NameRequiredDescriptionDefault
schematic_pathYesA .kicad_sch file of the project.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does add real behavioral context: results use the project's severities, and the tool goes beyond kicad-cli by additionally checking unannotated symbols, duplicate references, and units with mismatched values. It does not state that the operation is read-only or whether any files are written, which is the main remaining 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?

Two short sentences, front-loaded with the core action and followed by the differentiator. The phrase "annotation check of the ERC dialog" is stated twice in near-identical form, a small redundancy that costs nothing but adds no information.

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?

An output schema exists, so return values need not be explained, and the one-parameter surface is simple. However, the description never says how this differs from the other ERC-related siblings or what project context must be present, leaving an agent to guess between this and the report/violation tools.

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 100% and the single parameter is documented in the schema as a .kicad_sch file, so the description need not repeat it. It adds only the indirect implication that a project (for severities) must accompany the schematic, not the syntax or expectations for the path itself.

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 ("Run the ERC of kicad-cli on a schematic") and adds that it also performs the annotation check the CLI omits. It clearly separates itself from the PCB-side run_drc by naming ERC/schematic, though it does not explicitly distinguish itself from export_erc_report or get_erc_violations.

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?

Usage is implied: call this to check a schematic for electrical rule violations. There is no explicit when-to-use statement, no exclusion of the sibling reporting tools, and no mention of prerequisites such as the project file that supplies the severities.

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