Skip to main content
Glama

Audit PCB DFM Fabrication Rules

audit_pcb_dfm_rules
Read-onlyIdempotent

Check .kicad_pcb or .dsn files against standard 2-layer or 4-layer DFM limits for trace width, clearance, via hole diameter, and annular ring to catch fabrication issues early.

Instructions

Run a local Design-for-Manufacturing (DFM) rule check on a .kicad_pcb or .dsn file against standard 2-layer or 4-layer fabrication limits (minimum trace width, clearance, via hole diameter, and annular ring width).

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_pcb_dfm_rules"
  }
}

Input Schema

NameRequiredDescriptionDefault
fab_tierNoTarget fabrication rule tierstandard_2l
pcb_textNoRaw `.kicad_pcb` or `.dsn` file content
project_pathNoLocal path to `.kicad_pcb` or `.dsn` file

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.1.0
    • addedInput schema / properties / fab_tier / description
      Added value: +"Target fabrication rule tier"
  2. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds real value with 'local', signalling no upload to a cloud service (unlike the calligraphy_* siblings), and lists what is checked. It does not say what a check produces (pass/fail vs. violation list), since there is no output schema, which is a meaningful gap.

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?

A single front-loaded sentence with no filler, and the resource is stated before the parenthetical detail. The parenthetical rule list is dense but each item earns its place by telling the agent what will be measured.

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

Completeness3/5

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

For a 3-parameter, zero-required-parameter tool with no output schema, the definition leaves two important things unstated: how pcb_text and project_path interact (both optional, no precedence given) and what the check returns. Adequate but with clear gaps an agent would hit at invocation time.

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 the baseline is 3; the description adds the rule categories being evaluated. However it never explains the fab_tier enum's third value (fine_hdi), leaving the most consequential parameter choice unexplained beyond the one-word schema description.

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

Purpose4/5

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

Names a specific verb (run a DFM rule check) and resource (.kicad_pcb or .dsn file) and enumerates the exact limits checked (trace width, clearance, via hole diameter, annular ring), which clearly separates it from analyze_kicad_pcb or calligraphy_preflight_audit. Minor flaw: it says 'standard 2-layer or 4-layer' while the enum also offers fine_hdi, so the stated scope is narrower than the actual capability.

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

Usage Guidelines2/5

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

There is no explicit when-to-use or when-not-to-use guidance and no named alternative, so an agent must infer that this is a pre-fabrication gate rather than a general board analyzer. Nothing tells the caller when to choose fab_tier=fine_hdi over the standard tiers, nor when to prefer pcb_text over project_path.

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