Skip to main content
Glama
pcb-agent-mcp

pcb-agent-mcp

decoupling_check

Checks whether a decoupling capacitor network meets voltage-ripple and frequency-band requirements for a regulator load, using supply, current, ripple, bandwidth, and cap data.

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": {
      "vdd_v": "<vdd_v>",
      "load_current_a": "<load_current_a>",
      "ripple_mv": "<ripple_mv>",
      "band_hz": "<band_hz>",
      "caps": "<caps>"
    },
    "name": "decoupling_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
capsYes ...
vdd_vYes ...
band_hzYes ...
ripple_mvYes ...
r_series_ohmNo ...
load_current_aYes ...
regulator_bandwidth_hzNo ...

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 provides none. It does not say whether the check is read-only, what it validates, what a pass/fail means, or what the caller should expect back.

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?

There is no content to be concise about; the description is a bare placeholder rather than a short but informative statement. Nothing is front-loaded because nothing is stated.

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 7-parameter tool with 5 required inputs, no annotations, and no output schema depends entirely on the description for context, and the description is empty. An agent has no basis for calling this correctly beyond guessing from parameter names.

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 reported schema description coverage is 100%, which sets the baseline at 3 per the rubric, even though the description itself adds nothing. Note that the visible schema field descriptions are themselves placeholder ellipses, so the nominal coverage likely overstates real documentation and the effective score is closer to 2.

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. The only signal of purpose is the tool name itself, which the description merely fails to restate. An agent cannot distinguish this from siblings such as dfm_check or pdn_impedance based on the text.

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 guidance on when to use this tool, when not to, or which sibling (dfm_check, pdn_impedance, current_capacity) it complements. No prerequisites, no conditions, no alternatives.

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