Skip to main content
Glama
pcb-agent-mcp

pcb-agent-mcp

creepage_required

Calculate required PCB creepage and clearance distances from voltage, safety standard, pollution degree, and insulation type to verify compliant 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": {
      "voltage_v": "<voltage_v>",
      "safety_standard": "<safety_standard>"
    },
    "name": "creepage_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 supplied, so the description carries the full disclosure burden and delivers none of it: no statement of what standard/unit system is assumed, whether the result is advisory or authoritative, or what happens with defaults left unset. Nothing beyond the raw signature is communicated.

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 placeholder text " ..." is an unfilled stub rather than a structured, front-loaded description.

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 nine-parameter electrical-safety calculation with no output schema and no annotations needs a real description to be callable with confidence; the empty string leaves the agent without units, return shape, or interpretation guidance.

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?

All nine parameters carry schema descriptions (100% coverage), including two enums, so the agent can still interpret inputs from the schema alone; this is the baseline case where the schema does the heavy lifting. The description adds no meaning about how voltage, transient, coating and pollution degree interact, which for a domain-calculation tool would have been the valuable addition.

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 nothing states what the tool computes or returns. Only the name 'creepage_required' hints at a creepage-distance calculation, and that inference is left entirely to the agent; the sibling 'clearance_required' is not distinguished from it in any way.

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 text at all, so no guidance on when to use this versus clearance_required or the other calculation tools. The agent has to guess from the name alone.

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