Skip to main content
Glama
pcb-agent-mcp

pcb-agent-mcp

board_fidelity

Checks PCB design files for fidelity by parsing KiCad or EDA Pro formats, helping you catch mismatches and data loss before fabrication.

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

Input Schema

NameRequiredDescriptionDefault
pathYes ...
engineNo ...
formatNo ...

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 provided, so the description carries the full behavioral burden, and it is empty. It does not say whether the tool reads or writes, whether it mutates the PCB file, what permissions it needs, or what it returns.

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?

An empty placeholder is not concise, it is under-specified; there is no front-loaded statement of purpose or any structure to evaluate.

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 tool that apparently operates on a PCB file with an engine toggle and two format backends, and with no output schema, the definition provides zero information needed to invoke it correctly.

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?

The schema structurally declares three parameters (path required, engine boolean defaulting true, format enum kicad_pcb/epro), but their description fields are also placeholders, so no meaning is added about what path points to or when engine/format matter. The description contributes nothing beyond the raw schema types.

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 a placeholder string (" ...") that conveys nothing about what board_fidelity does. The name hints at some fidelity check on a board, but no verb, resource, or scope is stated, and nothing distinguishes it from siblings like board_drc, board_summary, or epro_inspect.

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 prerequisites, and no mention of alternatives among the many board_* and epro_* siblings. An agent has no basis for choosing this tool over board_drc or board_view.

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