Skip to main content
Glama

trace_netlist_connection

Trace component pin connections from a KiCad netlist by returning the nets for each pin and all pins on those nets; optionally filter to one pin.

Instructions

Give the nets of the pins of a component, and the pins on each net.

The netlist of kicad-cli is the most exact source for the connections. Make it with generate_netlist, and again after a change of the schematic.

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": {
      "netlist_path": "<netlist_path>",
      "reference": "<reference>"
    },
    "name": "trace_netlist_connection"
  }
}

Input Schema

NameRequiredDescriptionDefault
referenceYesThe reference of the component, for example "R16".
pin_numberNoOptional pin number, for example "1". Empty: all pins.
netlist_pathYesA netlist file of generate_netlist.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations supplied, the description must carry the behavioral burden; it does disclose that it is a pure read over a pre-generated netlist file and that this netlist is the most exact source of connectivity. It says nothing about error behavior for a missing/invalid netlist_path or about result size for large components.

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?

Very short and front-loaded, with the return shape stated first and the prerequisite second. The wording 'Give the nets of the pins' is slightly awkward, but no sentence is wasted.

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 netlist prerequisite is covered. For a three-parameter read tool that is mostly adequate, though the absence of any guidance on stale netlists or failure modes leaves a small gap.

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 reference, pin_number (empty means all pins), and netlist_path are already documented in the schema. The description adds no syntax or format detail beyond noting that a netlist produced by generate_netlist is the expected input.

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 states a specific verb and resource: it returns the nets attached to a component's pins and the pins belonging to each net, scoped by component reference. That is concrete enough to distinguish it from netlist-listing siblings like get_netlist_nets, though it never explicitly contrasts itself with trace_hierarchical_connection.

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?

It gives a clear prerequisite workflow: create the netlist with generate_netlist, and regenerate it after a schematic change, which implies this tool is used against a freshly produced netlist. It offers no explicit when-not guidance or comparison to the alternative hierarchical tracing tool.

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