Skip to main content
Glama
pcb-agent-mcp

pcb-agent-mcp

width_for_impedance

Calculate the PCB trace width needed to hit a target impedance from dielectric thickness, supporting microstrip and stripline with adjustable Er and copper thickness.

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": {
      "target_ohm": "<target_ohm>",
      "dielectric_mm": "<dielectric_mm>"
    },
    "name": "width_for_impedance"
  }
}

Input Schema

NameRequiredDescriptionDefault
erNo ...
kindNo ...
copper_umNo ...
target_ohmYes ...
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 disclosure burden, yet it is empty. Nothing is said about whether the result is a recommendation versus a geometry mutation, what units or assumptions apply, or whether any state changes occur.

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?

The description contains no content at all, so there is no structure or front-loading to assess. Under-specification of this degree is 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?

With five parameters, two required, no annotations, and no output schema, the description was the only channel to explain the calculation and its result. It delivers nothing, leaving the definition materially incomplete for an agent that must call it correctly.

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% across all five parameters, including the microstrip/stripline enum and the defaults for er and copper_um, so the schema alone documents the inputs. The description contributes no additional meaning, which puts it at the baseline for a well-documented schema rather than above it.

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 placeholder (" ...") and states nothing about what the tool does. Only the name hints that it computes a trace width for a target impedance, and the title is null, so an agent gets no verb-plus-resource statement to distinguish it from siblings like trace_impedance or diff_impedance.

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 when not to use it, and no routing to alternatives such as trace_impedance or diff_impedance. The agent must guess from the name alone which impedance tool applies.

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