Skip to main content
Glama

find_tracks_by_net

Retrieves all tracks and vias for a given net in a KiCad board file, returning each segment's length and width for analysis.

Instructions

Give the tracks and the vias of one net of a board, with their lengths and widths.

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

Input Schema

NameRequiredDescriptionDefault
net_nameYesThe name of the net.
file_pathYesThe .kicad_pcb file.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/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 burden; it does disclose that the result is the per-net track/via geometry with lengths and widths, which implies a read-only lookup. It says nothing about failure behavior for an unknown net name, units of measurement, or cost on large boards, which are the details an agent would still want before calling.

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 zero filler, though the phrasing 'Give the tracks and the vias' is slightly informal for a tool description and the result attributes are tacked on as a trailing clause.

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

Completeness4/5

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

For a simple two-parameter read tool with a fully documented schema and an output schema that covers the return shape, the description supplies the essential scope (one net, both tracks and vias, geometry attributes). Only the failure/units caveats are missing, which is a minor gap at this complexity.

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 parameters are already documented in the schema, and the description only restates that net_name refers to a net on the given board file. No format examples, path conventions, or naming rules are added beyond the schema.

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 concrete verb and resource: retrieve the tracks and vias belonging to one net of a board, and names the data returned (lengths and widths). It reads clearly and distinctly from catalog-style siblings like get_netlist_nets or analyze_pcb_nets, though it never explicitly contrasts itself with them.

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 explicit when-to-use statement, no prerequisites (e.g. the board must be parsed first), and no named alternative for cases such as needing all nets or needing aggregate analysis. Usage is only inferable from the phrase 'one net of a board'.

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