Skip to main content
Glama

get_erc_violations

Retrieve electrical rule check (ERC) violations from a KiCad schematic and filter results by severity (error or warning) to identify and resolve design issues.

Instructions

Give the ERC violations of a schematic, with a filter by severity.

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

Input Schema

NameRequiredDescriptionDefault
severityNoOptional severity: "error" or "warning". Empty: all violations.
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

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden. It does not disclose whether the tool triggers an ERC run (potentially expensive) or only reads prior results, nor any prerequisites such as the schematic needing to exist or be open. 'Give' implies a read, but that is not stated.

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?

One short, front-loaded sentence with no filler or redundancy. It is efficient, though its brevity is part of why behavioral and usage information is missing.

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 no explanation, and the two parameters are fully documented in the schema. However, the unresolved run-vs-read ambiguity and the absence of any sibling routing leave a meaningful gap for a tool whose cost profile depends on that distinction.

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 are already documented in the schema, including the severity enum values and the empty-string default. The description's mention of severity filtering adds no syntax or behavior beyond that; 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: retrieve ERC violations for a schematic, with a severity filter. It does not distinguish itself from siblings like run_erc or get_drc_violations, so an agent cannot tell from this sentence alone whether it executes a check or merely reports stored results.

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 when-to-use guidance at all. The description never says whether ERC must have been run first, nor when to prefer this over run_erc or export_erc_report, leaving the most consequential selection decision to inference.

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