Skip to main content
Glama

Calculate PCB Trace Impedance & IPC-2152 Current

calculate_pcb_trace_impedance
Read-onlyIdempotent

Calculates PCB microstrip/stripline impedance, differential impedance, propagation delay, and recommended trace width for target impedance or DC current using IPC-2141A and IPC-2152.

Instructions

Local PCB transmission-line impedance & IPC-2152 trace current calculator. Computes single-ended microstrip/stripline Z0 (Ohms), edge-coupled differential Zdiff (Ohms), propagation delay (ps/mm), and recommended trace width for a target impedance or DC current (Amps).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "calculate_pcb_trace_impedance"
  }
}

Input Schema

NameRequiredDescriptionDefault
erNoRelative permittivity Er of substrate (FR-4 = 4.4)
modeNoTransmission-line geometry (microstrip or stripline)microstrip
current_ampsNoTarget DC current in Amps for IPC-2152 temp rise check
trace_width_mmNoTrace width W in mm
max_temp_rise_cNoMaximum allowed temperature rise in Celsius
copper_weight_ozNoCopper weight in oz/ft^2 (1.0 oz = 0.035 mm)
trace_spacing_mmNoEdge-to-edge spacing S in mm for differential pair
dielectric_height_mmNoDielectric height H to reference plane in mm

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.1.0
    • addedInput schema / properties / mode / description
      Added value: +"Transmission-line geometry (microstrip or stripline)"
  2. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

The annotations already declare it read-only, idempotent, non-destructive, and closed-world; the description reinforces this with 'Local', meaning no board file or network access is involved. Beyond that it only enumerates output quantities, without saying how modes alter the calculation, whether differential results are always returned, or what happens if only defaults are supplied.

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?

Two dense sentences, front-loaded with the tool's identity and followed by the computed quantities with units. No filler, no repetition of the title, and the output list is compactly enumerated.

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?

With no output schema, the description usefully enumerates the four kinds of results an agent gets back and their units, which is the main gap otherwise. It remains slightly incomplete for an 8-parameter calculator: all parameters are optional with defaults, and the description never clarifies whether that yields a reference/default stackup result or which outputs are meaningful per mode.

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 100%, so every parameter already carries its own description and defaults, and the baseline is 3. The description adds units for the outputs (Ohms, ps/mm, Amps) and ties the mode to geometry, but adds no new meaning about parameter interactions or which inputs matter for which calculation.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb ('Computes') and concrete resources: microstrip/stripline Z0, edge-coupled differential Zdiff, propagation delay, and recommended trace width. It also positions the tool as a 'Local ... calculator', which separates it cleanly from the analysis/audit/routing siblings in a glance.

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?

Usage is only implied: an agent can infer you call this to size traces or check impedance for a given stackup, but there is no explicit statement of when to use this versus analyze_kicad_pcb or audit_pcb_dfm_rules, and no exclusions or prerequisites (e.g., 'call before routing', 'does not read a board file').

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