Skip to main content
Glama

get_netlist_components

Retrieve components from a KiCad netlist file with the nets of their pins, optionally filtered by reference prefix. Use it to map nets to pins before BOM or design checks.

Instructions

Give the components of a netlist file with the nets of 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_components"
  }
}

Input Schema

NameRequiredDescriptionDefault
filter_refNoOptional start of the references to give, for example "R", "U" or "C" (the case is important). Empty: all components.
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

C2.9/5.0
Behavior2/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. 'Give' weakly implies a read, but nothing states that it is non-mutating, whether it can fail on a malformed path, how large a netlist is tolerated, or how pins with no net are represented. Only the return-shape burden is lifted, and that is by the output schema rather than the text.

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 sentence with no filler and the essential content front-loaded. The phrasing 'Give the components ... with the nets of their pins' is slightly informal but wastes no words.

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 parameters, one required, output schema present), so the description need not explain return values. However, it omits the prerequisite relationship to generate_netlist and any routing versus get_netlist_nets, which an agent needs to pick and order calls correctly.

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%, documenting both netlist_path and the filter_ref prefix semantics (case sensitivity, empty meaning all), so the schema already does the heavy lifting. The description adds no parameter meaning beyond it, which is the expected baseline at full coverage.

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 names a specific verb-and-resource pair: it returns the components of a netlist file together with the nets attached to their pins. That output content is concrete enough for an agent to distinguish it from a purely net-oriented sibling like get_netlist_nets. It stops short of naming any sibling explicitly, so 4 rather than 5.

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 statement of when this tool should be chosen, no prerequisite (that the path must come from generate_netlist is only visible in the schema), and no reference to an alternative tool. The agent must infer usage entirely from the purpose sentence.

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