Skip to main content
Glama
pcb-agent-mcp

pcb-agent-mcp

current_capacity

Calculate PCB trace current-carrying capacity from trace width, copper weight, layer, and allowed temperature rise using IPC-2221 or IPC-2152 standards.

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": {
      "width_mm": "<width_mm>",
      "standard": "<standard>"
    },
    "name": "current_capacity"
  }
}

Input Schema

NameRequiredDescriptionDefault
layerNo ...
standardYes ...
width_mmYes ...
copper_ozNo ...
delta_t_cNo ...
mask_openingNo ...

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. Nothing states whether this is a pure lookup or a mutation, what the result represents (a capacity value? a pass/fail?), or what units and assumptions (e.g., IPC-2221 vs IPC-2152 default curves) apply.

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 an empty placeholder string. 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?

For a 6-parameter engineering calculation with no annotations and no output schema, the description should at minimum state what is computed, in what units, and under which standard. None of that is present, so the definition is not callable with confidence.

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% with 6 parameters, 2 of which are enums (layer, standard), so the schema is nominally the source of parameter meaning and the baseline is 3. The description adds nothing beyond the schema, and the per-parameter text in the supplied schema itself appears to be placeholder ellipses, which makes this a weak 3 rather than a strong one.

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 (" ...") with no verb, resource, or scope stated. The name current_capacity is the only signal an agent gets, and it does not distinguish this tool from siblings such as via_current_allowed or width_for_current.

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 exclusions, and no reference to any alternative. An agent has no basis for choosing this tool over via_current_allowed or width_for_current, which appear to cover adjacent IPC current/width questions.

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