Skip to main content
Glama

analyze_hierarchical_nets

Analyzes every net in a full KiCad schematic hierarchy, classifies nets as power, interface, or signal by name, and returns sheet paths for connectivity review.

Instructions

Analyze all nets of the full schematic hierarchy.

The tool reads the netlist that kicad-cli writes now: the nets of all sheets at each level of the hierarchy. It groups them as power, interface and signal nets (by their names), and gives the sheet paths of the hierarchy.

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

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).
filter_patternNoOptional regular expression for the net names (no difference of case). Empty: all nets.
show_hierarchyNoTrue (default): list the sheet paths of the hierarchy with their files.

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 carries the full burden and does disclose several useful traits: the data source is the kicad-cli-written netlist, all hierarchy levels are covered, and the power/interface/signal grouping is a name-based heuristic (useful for interpreting classification surprises). It stops short of stating read-only nature, cost/performance on large hierarchies, or what happens with flat/unannotated schematics.

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?

Front-loaded with the purpose in the first sentence, followed by two compact supporting sentences covering data source and output content. Slightly awkward phrasing ('the netlist that kicad-cli writes now') but no filler sentences.

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 description adequately covers source and grouping. For a read-only analysis tool with no annotations and 3 params it is nearly sufficient, but it omits the flat-schematic edge case and any performance or permission expectations.

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 coverage is 100%, so the baseline is 3. The description adds only indirect meaning: 'gives the sheet paths of the hierarchy' maps loosely to show_hierarchy and 'by their names' hints at net-name matching used by filter_pattern, but no parameter is addressed directly with behavior or format detail.

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 scope ('analyze all nets of the full schematic hierarchy') and adds what the output contains: nets grouped as power/interface/signal plus sheet paths. The scope word 'hierarchy' implicitly separates it from flat netlist siblings like get_netlist_nets, but no sibling is named explicitly.

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 is only implied: the description signals this is the hierarchy-wide net analysis, so an agent can infer it should be preferred over flat net listings when hierarchy context matters. There is no explicit when-to-use/when-not guidance and no named alternative for single-sheet cases.

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