Skip to main content
Glama
pcb-agent-mcp

pcb-agent-mcp

width_for_current

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

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": {
      "current_a": "<current_a>",
      "standard": "<standard>"
    },
    "name": "width_for_current"
  }
}

Input Schema

NameRequiredDescriptionDefault
layerNo ...
standardYes ...
copper_ozNo ...
current_aYes ...
delta_t_cNo ...

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?

With no annotations provided, the description carries the full burden of behavioral disclosure, and it provides none. It says nothing about whether this is a pure calculation, what standard the result assumes, or what the caller receives 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?

The description is an empty placeholder (' ...') with no sentence structure, no front-loaded purpose, and no usable content. There is no waste because there is no content at all — that is 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?

This is a five-parameter engineering calculation with no annotations and no output schema, so the description is the only place an agent could learn assumptions like applicable IPC standard behavior or unit conventions. It says nothing, leaving the definition wholly inadequate for the tool's complexity.

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 100%, so all five parameters (layer, standard, copper_oz, current_a, delta_t_c) are already documented in the schema, and the enums constrain two of them. The description adds no extra meaning, but the high-coverage baseline of 3 applies since the schema does the work.

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 the literal placeholder '" ..."' and conveys nothing about what the tool does. Only the name 'width_for_current' hints at a trace-width-from-current calculation, and the description neither confirms nor elaborates on that.

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?

No when-to-use guidance, no exclusions, and no routing to the obvious siblings such as 'width_for_impedance' or 'current_capacity'. An agent must guess the intended use case purely from the tool name.

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