Skip to main content
Glama

add_trace

Connects two ports or nets with a schematic trace in a circuit file, letting you define connections such as ".R1 > .pin1" to "net.GND" without adding copper.

Instructions

Schematic trace (a connection, no copper): connect two ports or nets, e.g. from ".R1 > .pin1" to "net.GND".

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": "<file>",
      "from": "<from>",
      "to": "<to>"
    },
    "name": "add_trace"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYes
fileYesCircuit file
fromYes
propsNoExtra trace props, e.g. { "thickness": "0.4mm" }

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/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 behavioral burden, and it only discloses that the result is a schematic connection with no copper. It says nothing about how the circuit file is affected (in-place mutation vs. return), what happens if the ports/nets don't resolve, or whether duplicate traces are permitted — all material for an additive mutation tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One compact sentence that front-loads the core definition, then the scope qualifier, then a concrete example. Nothing is wasted and the most decision-relevant information comes first.

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?

For a 4-parameter mutation with no annotations and no output schema, the definition covers purpose and argument syntax but leaves side effects, failure modes, and return behavior unstated. Adequate to attempt a call, but not complete enough to predict the outcome confidently.

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 50% ('file' and 'props' are described, 'from'/'to' are bare strings). The description compensates well for the gap by giving concrete syntax examples ('.R1 > .pin1', 'net.GND'), which is real added meaning beyond the schema, but it says nothing about the undocumented 'props' interplay or validation rules. Given the mixed coverage, a 3 fits.

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 ('connect') and resource ('two ports or nets'), and clarifies it creates a schematic trace rather than copper. That schematic-vs-copper distinction separates it from PCB-side siblings like autoroute or fillet_tracks, though 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 Guidelines4/5

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

The parenthetical '(a connection, no copper)' implicitly tells the agent this is for schematic connectivity, not PCB routing, which is a useful exclusion. It does not, however, point to alternatives such as connect_nets or explain prerequisites (e.g. that the file and referenced ports must already exist).

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