Skip to main content
Glama
pcb-agent-mcp

pcb-agent-mcp

board_drc

Run design rule checks on PCB layouts to detect violations, filter results by severity, and optionally refill zones before reporting errors.

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": {
      "path": "<path>"
    },
    "name": "board_drc"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYes ...
limitNo ...
strictNo ...
projectNo ...
severityNo ...all
timeout_sNo ...
backgroundNo ...
refill_zonesNo ...

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.43

TDQS

D1.2/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 behavioral burden, and it discloses nothing. Whether the tool reads or writes the board, whether it is safe to run repeatedly, whether it is long-running (the timeout_s and background params hint at that), and what it returns are all undisclosed.

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 structure to evaluate — the entire description is an unfilled placeholder. This is under-specification rather than 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?

An 8-parameter tool with timeout and background options, no annotations, and no output schema is entirely undocumented. An agent has no basis to decide when to invoke it, what the parameters do, or how to interpret results.

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

Parameters2/5

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

Schema coverage is reported as 100%, but every parameter description in the supplied schema is itself a " ..." placeholder, so no meaning is actually conveyed there either. Parameter names (limit, strict, severity, timeout_s, background, refill_zones, project, path) are partly self-explanatory and the severity enum is visible, but the description adds zero clarification for behaviorally significant flags like strict, refill_zones, and background.

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 literally " ...", a placeholder with no content. Only the tool name 'board_drc' hints at a design-rule-check operation; nothing states what it checks, on what input, or how it differs from siblings like board_rules, board_fidelity, dfm_check, or clearance_required.

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 prerequisites, no mention of alternatives. An agent cannot tell whether this is the right tool versus board_rules, dfm_check, or clearance_required, all of which plausibly overlap with rule checking.

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