Skip to main content
Glama

audit_find_pads_near_board_edge

Detect PCB pads and vias closer than a specified clearance to the board outline to prevent depaneling damage during v-cut or mouse-bite separation.

Instructions

Find PCB pads / vias closer than clearance_mils to the board outline (depaneling damage hazard).

Copper too close to the routed edge gets scuffed / scored / torn during v-cut + mouse-bite break. IPC-2221 and typical fab houses want at least 20-50mil clearance for critical components, more for connectors. Worth tightening to 50+ for boards going to depaneling rather than rounded-corner manufacture.

The gap is measured from the outline's own segments, lines and arcs, to the pad's copper: a via or round pad by its radius, a rectangle by its nearest corner or edge midpoint, at whatever rotation. Round and other curved outlines are covered.

Args: clearance_mils: Minimum gap to flag as a violation (default 25). Try 50 if your fab depanels by v-cut.

Returns: Dict with: - checked: total pads + vias inspected - violations: how many are within the clearance - unmeasured: pads that could not be measured, which are therefore neither passed nor flagged - clearance_mils: echo of the threshold used - items: per-violation {kind, designator, distance_mils, at} where at is "(x,y)" mils.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "audit_find_pads_near_board_edge"
  }
}

Input Schema

NameRequiredDescriptionDefault
clearance_milsNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.1

TDQS

A4.3/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the full burden and does well: it explains what is measured (outline segments to pad copper, per-shape geometry), discloses the 'unmeasured' caveat, and implies a read-only audit. It never explicitly states it does not modify the board, which keeps it from a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Purpose is front-loaded in sentence one, followed by useful rationale and measurement semantics. The Returns block is somewhat redundant given an output schema exists, adding length that the schema already covers.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a single-parameter audit tool the description covers purpose, measurement methodology, threshold selection, and result interpretation. Since an output schema exists, the verbose Returns section is more than needed but not harmful.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0% (no description on clearance_mils), so the description must compensate, and it does: units in mils, meaning as the flag threshold, the default of 25, and tuning advice. Only the absence of format/range constraints keeps it below 5.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The first sentence states a specific verb and resource: find PCB pads/vias closer than clearance_mils to the board outline. It names the hazard (depaneling damage) so an agent can distinguish it from sibling audits like audit_find_components_outside_board_outline.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives concrete threshold guidance ('Try 50 if your fab depanels by v-cut') and background on IPC-2221/fab expectations, so the agent knows how to configure it. It does not explicitly name an alternative tool or state when not to use it, so it stops short of a 5.

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

Deploy Server

Other Tools