Skip to main content
Glama

trace_hierarchical_connection

Trace a component's connections across every sheet in a KiCad schematic hierarchy by reading the root netlist, with an optional pin filter.

Instructions

Trace the connections of a component across the full schematic hierarchy.

The tool reads the netlist that kicad-cli writes now: it has each component of each sheet path, at each level of the hierarchy, with the reference of that path (a sheet that the hierarchy uses two times gives two references). The netlist has no power symbols and no symbol with no library symbol. The tool needs kicad-cli.

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": {
      "file_path": "<file_path>",
      "reference": "<reference>"
    },
    "name": "trace_hierarchical_connection"
  }
}

Input Schema

NameRequiredDescriptionDefault
file_pathYesA .kicad_sch file of the project (the root schematic or a sub-sheet: the tool uses the netlist of the root schematic).
referenceYesThe reference of the component, for example "U1".
pin_numberNoOptional pin number. Empty: all pins.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/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 well: it discloses the data source (the netlist kicad-cli writes), that references are per sheet path so a reused sheet yields multiple references, and that power symbols and symbols lacking a library symbol are absent. It does not state the operation is read-only or what happens when the reference is not found, but the read-only nature is strongly implied by 'Trace'/'reads'.

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?

The purpose is front-loaded in the first sentence and the remaining text is substantive rather than filler. The kicad-cli dependency is stated twice (mid-paragraph and again at the end), which is minor redundancy in an otherwise tight description.

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-value explanation is not needed, and all three parameters are documented in the schema. However, for a hierarchy-aware trace tool the description omits expected failure modes (reference not in netlist, component on a sheet not instantiated) and any guidance on interpreting per-path results, leaving gaps for an agent calling it blind.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3; the description earns above that by explaining that file_path may be the root or a sub-sheet while the netlist of the root is used, and by noting that a sheet used twice produces two references, which explains why a 'reference' may be ambiguous. It adds no further detail on pin_number beyond the schema.

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 definition gives a specific verb and resource ('Trace the connections of a component') plus the scope qualifier 'across the full schematic hierarchy', which distinguishes it in spirit from a flat netlist trace. It does not name trace_netlist_connection, so the sibling differentiation is left implicit.

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 context is implied by the hierarchy framing and the note that the tool uses the root schematic netlist even when given a sub-sheet, which is genuinely useful. There is no explicit statement of when to prefer this over manual/AI inspection of the netlist or a non-hierarchical trace, and no exclusions.

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