Skip to main content
Glama

list_schematic_nets

Extract the net names from a KiCad schematic file by reading its labels and power symbols, with an option to filter power nets only. Use full hierarchy netlists for sub-sheet nets.

Instructions

Give the nets of a schematic file.

The tool reads the labels and the power symbols of the file. A net with no label of a sub-sheet needs the full hierarchy: use generate_netlist on the root schematic for all nets.

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>"
    },
    "name": "list_schematic_nets"
  }
}

Input Schema

NameRequiredDescriptionDefault
file_pathYesA .kicad_sch file of the project.
filter_powerNoTrue gives only the nets whose name has "gnd", "vcc", "vdd", "vss", "+" or "-" (heuristic).

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full disclosure burden. It usefully reveals how nets are derived (from labels and power symbols) and a genuine extraction limitation for unlabeled sub-sheet nets, but says nothing about read-only safety, error behavior on a bad path, or performance on large files.

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?

Three short sentences with the core action front-loaded and no filler. The line breaks split a single idea awkwardly, but no sentence is redundant.

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

Completeness5/5

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

For a two-parameter read tool with an output schema, the description covers purpose, derivation method, and the key scope limitation that would otherwise cause a wrong tool choice. Nothing an agent needs in order to call it correctly is missing.

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 file_path and the filter_power heuristic are already fully documented in the schema. The description adds only indirect meaning by explaining that nets come from labels and power symbols, which does not extend the parameter semantics beyond what is structured.

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 first sentence pairs a concrete verb with a concrete resource ("Give the nets of a schematic file"), which lets an agent distinguish this from PCB-side siblings like analyze_pcb_nets. It also names generate_netlist as the hierarchy-wide alternative, though the phrasing "A net with no label of a sub-sheet needs the full hierarchy" is awkward enough that the distinction takes a second read.

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?

The description states a clear exclusion: when nets come from unlabeled sub-sheets, use generate_netlist on the root schematic instead. It does not address other plausible alternatives (analyze_hierarchical_nets, get_netlist_nets) or say when this single-file read is preferable, so the guidance is real but partial.

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