Skip to main content
Glama
pcb-agent-mcp

pcb-agent-mcp

via_current_allowed

Calculates allowable current for PCB vias from hole diameter, plating thickness, conductor count, and temperature rise using IPC-2221 or IPC-2152, so you can size vias for current-carrying designs.

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": {
      "hole_mm": "<hole_mm>",
      "standard": "<standard>"
    },
    "name": "via_current_allowed"
  }
}

Input Schema

NameRequiredDescriptionDefault
countNo ...
hole_mmYes ...
standardYes ...
delta_t_cNo ...
plating_umNo ...

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 discloses nothing: no statement about whether this is a pure calculation, what the result represents, units, or assumptions. The empty text leaves the agent with zero behavioral context.

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 a concise statement; there is no front-loaded purpose and nothing for the reader to use. Under-specification, not length, is the problem.

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 five-parameter engineering calculator with two required inputs, no annotations, and no output schema needs a description explaining the computed quantity and its units. The definition supplies none of that, so an agent cannot responsibly invoke it.

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 each of the five parameters (hole_mm, standard enum, count, delta_t_c, plating_um) is documented in the schema itself. The description adds no meaning beyond that, but with full schema coverage the baseline of 3 applies.

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 only " ...", a placeholder with no verb, resource, or statement of what is computed. The name via_current_allowed hints at a current-carrying calculation, but the definition itself supplies no purpose an agent could rely on.

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 mention of prerequisites, and no reference to related tools such as current_capacity or thermal_via_array. An agent has nothing to distinguish this from sibling calculators.

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