Skip to main content
Glama
pcb-agent-mcp

pcb-agent-mcp

ir_drop_chain

Computes IR drop across a series of PCB trace segments using current and temperature, helping identify excessive voltage loss in power delivery paths.

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": {
      "segments": "<segments>",
      "current_a": "<current_a>"
    },
    "name": "ir_drop_chain"
  }
}

Input Schema

NameRequiredDescriptionDefault
temp_cNo ...
segmentsYes ...
current_aYes ...

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 provided, so the description carries the full behavioral burden, and it discloses nothing: not whether the tool is read-only or mutating, not what permissions or board context it needs, not what the result represents. The empty string leaves all behavioral traits completely undisclosed.

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 is an empty placeholder rather than prose, so there is nothing front-loaded and nothing that earns its place. This is severe under-specification, 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 tool with two required parameters, a nested segments array, a physical-units input (current_a, temp_c), no annotations, and no output schema, the description should explain inputs, units, and result meaning. It provides none of that, leaving the definition unusable without external inference.

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 reported at 100%, so per the baseline rule the schema is treated as documenting the three parameters (segments, current_a, temp_c) and the description is not required to compensate. The description itself adds zero meaning, however, and the visible schema descriptions are themselves ellipses, so this is a floor-level pass rather than a real contribution.

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 (" ..."), so it states no verb, no resource, and no scope. An agent must infer entirely from the tool name that this computes IR drop along a chain; there is no textual evidence of what the tool does or how it differs from siblings such as pdn_impedance or current_capacity.

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. The description contains no informational content at all, so nothing routes the agent between this tool and the many other electrical-analysis siblings.

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