Skip to main content
Glama
pcb-agent-mcp

pcb-agent-mcp

clearance_required

Calculates required PCB electrical clearance and creepage distances from voltage, safety standard, pollution degree, insulation type, altitude, and coating inputs.

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": {
      "voltage_v": "<voltage_v>",
      "safety_standard": "<safety_standard>"
    },
    "name": "clearance_required"
  }
}

Input Schema

NameRequiredDescriptionDefault
coatingNo ...
voltage_vYes ...
altitude_mNo ...
insulationNo ...
transient_vNo ...
pcb_materialNo ...
material_groupNo ...
safety_standardYes ...
pollution_degreeNo ...

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. There is no indication of whether this is a pure calculation, what standard/assumption set is applied, whether results include margins, or what the response contains.

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 text is not concise but absent: an ellipsis placeholder conveys zero information. There is no front-loaded purpose statement or structure to evaluate.

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 9-parameter domain calculation tool with no annotations and no output schema, the definition supplies none of the context an agent needs — no method, no standards basis, no return shape. The rich schema cannot compensate for a completely empty description.

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 nine parameters (voltage_v, safety_standard, insulation enum, pollution_degree, etc.) are already documented in the schema with defaults and enums. Per the baseline rule for high coverage, a 3 applies even though the description adds no parameter meaning of its own.

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. Neither the title (null) nor the text explains what clearance_required computes, so the agent must infer purpose from the tool name alone.

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 alternatives. The sibling list includes the closely related creepage_required, yet nothing tells the agent when to pick one over the other.

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