Skip to main content
Glama
pcb-agent-mcp

pcb-agent-mcp

trace_impedance

Calculate PCB trace impedance for microstrip or stripline geometries from trace width, dielectric thickness, copper thickness, and dielectric constant.

Instructions

...

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": {
      "width_mm": "<width_mm>",
      "dielectric_mm": "<dielectric_mm>"
    },
    "name": "trace_impedance"
  }
}

Input Schema

NameRequiredDescriptionDefault
erNo ...
kindNo ...
width_mmYes ...
copper_umNo ...
dielectric_mmYes ...

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.43

TDQS

D1.4/5.0
Behavior1/5

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

No annotations are supplied, so the description must carry the full behavioral burden, and it supplies nothing. It does not say whether this is a pure calculation, what units or assumptions apply, or how the result is returned.

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

Conciseness2/5

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

There is no wasted wording because there is essentially no wording at all. This is severe under-specification rather than conciseness, so it earns the same minimal score as a bare one-word description.

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

Completeness1/5

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

A five-parameter engineering calculator with no annotations and no output schema needs the description to explain the calculation model and result shape, and this one is empty. An agent cannot determine what the returned impedance value represents.

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 all five parameters (er, kind, width_mm, copper_um, dielectric_mm) are already documented in the schema and the required set is declared. The description adds nothing on top, but the baseline of 3 applies when the schema does the heavy lifting.

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

Purpose1/5

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

The description is the literal placeholder " ...", so it states no verb, no resource, and no scope. Nothing distinguishes trace_impedance from siblings such as diff_impedance or width_for_impedance beyond the bare tool name.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

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

There is no when-to-use guidance, no mention of alternatives, and no prerequisites or exclusions. An agent has no textual basis for choosing this tool over the related impedance calculators.

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