Skip to main content
Glama

add_via

Place a single manual via at specified coordinates in a circuit file, assigning the net from underlying copper unless overridden and optionally setting layers.

Instructions

Place a via by hand as ONE change; its net is that of the copper under it unless given.

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

Input Schema

NameRequiredDescriptionDefault
atYes
netNo
fileYesCircuit file
layersNoDefault ["top", "bottom"]

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations, the description carries the full burden but does disclose two real behaviors: the via is recorded as a single undoable change, and its net is inherited from underlying copper unless overridden. It says nothing about validation, DRC, error conditions, or what happens if `at` falls outside board bounds.

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 tight sentence with the primary action front-loaded and the default behavior following. The semicolon construction is dense but every clause carries information.

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

Completeness2/5

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

For a placement tool with a nested coordinate object, no annotations, and no output schema, the description omits essential context: coordinate units/frame, the minimum-two-layer constraint implied by the schema, and confirm/return behavior. An agent cannot call this reliably without guessing at units.

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 layers are documented, at and net are not). The description compensates for `net` by explaining its inheritance default, which is genuinely useful, but leaves `at` (nested x/y) with no units, origin, or coordinate-frame guidance.

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 resource ("Place a via") and adds a scope qualifier ("by hand"), which separates it from automated siblings like autoroute or autoplace. It does not explicitly contrast with add_trace or add_pour, but the action is unambiguous without opening the schema.

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?

"By hand" implies manual placement versus an automated router, but no alternative is named and no conditions for when-not-to-use are given. Usage context is inferable rather than stated.

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