Skip to main content
Glama

detect_pin_conflicts

Detects nets in a KiCad schematic that contain pin conflicts, flagging multiple output or driver pins, isolated single-pin nets, and unconnected pins before running a full ERC.

Instructions

Find the nets with pin conflicts in a schematic.

The pin types come from the netlist of kicad-cli. A net with more than one output or driver pin is an error. A net with one pin is a warning. A pin with no connection is information. Run run_erc for the full electrical check of KiCad.

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

Input Schema

NameRequiredDescriptionDefault
schematic_pathYesA .kicad_sch file of the project. The tool uses the components and the netlist of the full project.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does well: it discloses the data source (kicad-cli netlist), the severity model (multiple output/driver pins = error, single pin = warning, unconnected pin = information), and that the whole project's components are analyzed. It does not state that the operation is read-only or whether results are cached, which would round out the disclosure.

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?

Purpose is front-loaded in the first sentence, followed by the classification rules and then the sibling pointer. Every sentence contributes, though the metadata note about kicad-cli is the least essential line and the hard line wraps make it read as a wall of text.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a single-parameter read tool with an output schema and no annotations, the definition supplies source, severity semantics, and an alternative. What remains unsaid — read-only nature, scope of the returned nets — is minor given the output schema covers return values.

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?

The single parameter is fully documented in the schema (100% coverage), so baseline is 3. The description adds only a little beyond it by clarifying that the project's full component set and netlist are used, which tells the agent the path needn't point at a partial design.

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

Purpose5/5

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

States a specific verb and resource ('Find the nets with pin conflicts in a schematic') and immediately delineates itself from the sibling ERC tool by scoping itself to pin-level conflicts only. An agent can distinguish it from run_erc and get_erc_violations without opening any schema.

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

Usage Guidelines4/5

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

'Run run_erc for the full electrical check of KiCad' names the alternative and implies this tool is the narrower, pin-conflict-only check. It stops short of an explicit 'use this when you only care about pin drive conflicts' statement or any exclusion, so it is clear context rather than a complete routing rule.

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