Skip to main content
Glama
pcb-agent-mcp

pcb-agent-mcp

diff_impedance

Calculate differential impedance for PCB microstrip or stripline traces from width, spacing, dielectric thickness, and material properties to verify controlled-impedance routing.

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>",
      "spacing_mm": "<spacing_mm>",
      "dielectric_mm": "<dielectric_mm>"
    },
    "name": "diff_impedance"
  }
}

Input Schema

NameRequiredDescriptionDefault
erNo ...
kindNo ...microstrip
width_mmYes ...
copper_umNo ...
spacing_mmYes ...
dielectric_mmYes ...

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.43

TDQS

D1.3/5.0
Behavior1/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 of behavioral disclosure, and it discloses nothing: not whether this is a pure calculation, what units the result uses, what the output looks like, or any constraints on valid inputs.

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

Conciseness1/5

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

" ..." is an unfilled placeholder rather than prose, so there is no structure or front-loading to evaluate. This is under-specification at its most extreme, not conciseness.

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?

For a six-parameter engineering calculator with no output schema and no annotations, the description should at minimum state what is computed and in what units. Nothing is provided, so an agent cannot determine result semantics (e.g. ohms, differential vs single-ended) from the definition alone.

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 six parameters (er, kind, width_mm, copper_um, spacing_mm, dielectric_mm) are documented in the schema including the enum and defaults. Baseline 3 applies since the schema does the work the description omits.

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 a literal placeholder (" ...") and conveys nothing about what the tool does. Only the name and the parameter names hint at differential-impedance calculation; the description itself provides no verb, resource, or scope.

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?

No when-to-use guidance, no exclusions, and no mention of alternatives such as trace_impedance or width_for_impedance. An agent must guess whether this computes differential impedance or something else entirely.

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