Skip to main content
Glama
pcb-agent-mcp

pcb-agent-mcp

pdn_impedance

Compute PDN impedance versus frequency from capacitor, plane, and series-resistance inputs to assess decoupling performance and identify resonance issues.

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": {
      "freqs_hz": "<freqs_hz>",
      "caps": "<caps>"
    },
    "name": "pdn_impedance"
  }
}

Input Schema

NameRequiredDescriptionDefault
capsYes ...
planeNo ...
freqs_hzYes ...
r_series_ohmNo ...
plane_cap_faradNo ...

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 behavioral burden, and it discloses nothing about computation model, units/assumptions, failure modes, or what the caller gets back. For an analysis tool requiring caps, frequency points, and optional plane/ESR overrides, this is a complete gap.

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 to be concise about; it is an unfilled placeholder rather than a front-loaded summary. Nothing is structured or prioritized for the reader.

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 5-parameter engineering calculation tool with a nested object parameter, no output schema, and no annotations, the description is entirely absent. Nothing explains inputs' physical meaning, the model used, or expected results.

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 (caps, plane, freqs_hz, r_series_ohm, plane_cap_farad) are already documented in the schema. The description adds nothing beyond that, 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 an empty placeholder (" ..."), so it states no verb, resource, or scope at all. Only the tool name hints at power-delivery-network impedance, which is inference, not stated purpose.

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 text indicating when to use this tool, when not to, or how it differs from siblings such as diff_impedance, trace_impedance, or width_for_impedance. An agent must guess from names alone.

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