Skip to main content
Glama
pcb-agent-mcp

pcb-agent-mcp

dfm_check

Runs design-for-manufacturing checks on a PCB project path, validating clearance and capability rules to flag fabrication issues before production.

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>",
      "capability": "<capability>"
    },
    "name": "dfm_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYes ...
layerNo ...
memberNo ...
projectNo ...
window_mmNo ...
capabilityYes ...
check_clearanceNo ...

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 burden of behavioral disclosure and delivers nothing. It does not say whether the tool mutates the board, what it validates, what permissions it needs, or what it reports back.

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 description is a single truncated placeholder with no front-loaded purpose and no content at all. This is under-specification rather than conciseness, so it earns the bottom of the scale.

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 7-parameter tool with 2 required inputs, a nested object, and no annotations or output schema, the definition is completely inadequate. Nothing an agent needs in order to invoke dfm_check correctly is present.

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 reported at 100% across all 7 parameters, so the baseline of 3 applies even though the description adds no parameter meaning. Note that the visible schema descriptions are themselves placeholders, which limits how much the schema can actually compensate.

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 the literal placeholder string " ...", which states no verb, resource, or scope. An agent cannot determine from it what dfm_check actually checks or how it differs from siblings such as clearance_required or board_drc.

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 preconditions, and no mention of any alternative tool. The name hints at a design-for-manufacturability check, but nothing in the text routes the agent between this and the many other board check tools.

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