Skip to main content
Glama
pcb-agent-mcp

pcb-agent-mcp

via_resistance

Calculate barrel resistance from drill diameter, plating thickness, and length to estimate voltage drop and power loss in PCB power-integrity checks.

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": {
      "drill_mm": "<drill_mm>",
      "plating_um": "<plating_um>",
      "length_mm": "<length_mm>"
    },
    "name": "via_resistance"
  }
}

Input Schema

NameRequiredDescriptionDefault
countNo ...
temp_cNo ...
drill_mmYes ...
length_mmYes ...
plating_umYes ...
plating_outsideNo ...

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: no computation model, unit conventions, validity ranges, error behavior, or whether results are cached. The via_resistance return content is entirely undocumented.

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 single placeholder token conveys nothing and is not front-loaded information. This is under-specification rather than 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?

A 6-parameter engineering calculation tool with 3 required dimensional inputs (drill_mm, plating_um, length_mm), no annotations, and no output schema demands substantial descriptive context. The definition supplies none, leaving an agent unable to call it correctly or interpret 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 reported at 100% for all 6 parameters, so the schema is nominally the source of parameter meaning and the baseline of 3 applies. The description itself adds zero parameter meaning, and the visible schema descriptions appear to be placeholder text, which is a concern but cannot be attributed to the description.

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, no resource, and no scope. Only the tool name hints at computing via resistance; nothing distinguishes it from siblings such as via_current_allowed or thermal_via_array.

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, no exclusions, and no naming of alternatives. An agent has no textual basis for choosing this tool over the via-related sibling tools.

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