Skip to main content
Glama

get_netlist_nets

Extracts the nets and their pins from a KiCad netlist file, with an optional regex filter on net names, to inspect connectivity for schematic checks.

Instructions

Give the nets of a netlist file with their pins.

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

Input Schema

NameRequiredDescriptionDefault
netlist_pathYesA netlist file of generate_netlist.
filter_patternNoOptional regular expression for the net names (no difference of case). Empty: all nets.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden, yet it says nothing about whether the operation is read-only, what happens with an unreadable path, an invalid regex, or an empty result, or how large netlists are handled. The presence of an output schema relieves it of explaining return shapes, but the safety and failure profile is entirely undisclosed.

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?

A single front-loaded sentence with no filler or redundancy. It is efficient, though the terseness borders on under-specification rather than tightness.

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?

The tool is simple (two params, fully documented schema, output schema present), so the minimal description is not crippling. However, with no annotations at all, an agent gets no signal about side effects or failure modes, leaving genuine gaps for a tool reading arbitrary file paths.

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%: netlist_path is described as "A netlist file of generate_netlist" and filter_pattern documents the regex, case-insensitivity, and empty-means-all behavior. The description adds nothing beyond that, so the baseline of 3 is appropriate.

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?

"Give the nets of a netlist file with their pins" states a verb (list/return), a resource (nets), and a discriminating detail (pins, and netlist-file source as opposed to schematic or PCB sources named among siblings). It is clear enough to distinguish it from analyze_pcb_nets or list_schematic_nets, but it never names an alternative and the verb "give" is soft.

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

Usage Guidelines2/5

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

There is no when-to-use statement, no prerequisite (e.g. that the file must come from generate_netlist), and no routing to alternatives such as analyze_hierarchical_nets or trace_netlist_connection. The agent must infer the usage context entirely from the tool name.

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