Skip to main content
Glama
pcb-agent-mcp

pcb-agent-mcp

stackup_design

Calculates impedance-controlled PCB layer stack dimensions from material, layer count, frequency, copper thickness, board thickness, and target impedance.

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": {
      "layers": "<layers>",
      "material": "<material>"
    },
    "name": "stackup_design"
  }
}

Input Schema

NameRequiredDescriptionDefault
erNo ...
layersYes ...
freq_ghzNo ...
materialYes ...
total_mmNo ...
copper_umNo ...
target_ohmNo ...

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 carries the full disclosure burden, and it discloses nothing. It does not say whether the tool is read-only or mutating, whether it writes a stackup into the project, what gets produced, or whether inputs like material and target_ohm are validated or conflicting.

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?

The text is not verbose but is absent rather than concise; " ..." is an unfilled placeholder with no front-loaded purpose statement. Under-specification, not length, is the defect.

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 7-parameter engineering calculation with no annotations and no output schema, the description explains nothing about inputs, results, or units. An agent has no basis to invoke it correctly or to interpret what a computed stackup means.

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?

The input schema has 100% description coverage across all 7 parameters, including an enum for material, so the schema itself documents the contract. The description adds no meaning beyond it, but the baseline of 3 applies because 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 a literal placeholder (" ...") and conveys no verb, resource, or purpose. Nothing distinguishes stackup_design from siblings such as diff_impedance or board_rules, and an agent cannot tell what the tool produces or computes.

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 prerequisites, and no mention of alternatives. With a large sibling set around impedance and board-rule calculation, the absence of any routing guidance leaves selection entirely to guesswork from the name.

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