Skip to main content
Glama
pcb-agent-mcp

pcb-agent-mcp

board_view

Read a PCB board file and return structured details on nets, layers, stackup, footprints, pads, tracks, vias, zones, and outline for design review and automation.

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

Input Schema

NameRequiredDescriptionDefault
kindNo ...all
pathYes ...
limitNo ...
memberNo ...
offsetNo ...
max_bytesNo ...
include_rawNo ...

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 behavioral burden, and it discloses nothing: no read-only vs. mutating nature, no truncation behavior despite max_bytes/limit/offset parameters, no permission requirements. The 'deleted' and 'uninterpreted' enum members in the schema hint at meaningful behavior the description never explains.

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 an empty placeholder rather than prose, so there is no front-loading, structure, or economy to evaluate. This is under-specification, not 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?

A 7-parameter tool with an 18-value kind enum, no annotations, and no output schema needs a description to explain what a 'view' returns and how pagination/truncation behaves. None of that is present, leaving the definition wholly inadequate for correct invocation.

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 seven parameters (kind, path, limit, member, offset, max_bytes, include_raw) are already documented in the schema and the description adds nothing. Baseline 3 applies because the schema does all the work, but the description contributes zero meaning about parameter interactions or defaults.

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 placeholder text " ..." and states no verb, resource, or scope. Nothing distinguishes board_view from siblings such as board_summary or board_components, so an agent cannot tell what the tool returns or does.

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, when-not-to-use, or alternative guidance of any kind. The sibling list contains clearly overlapping tools (board_summary, board_nets, board_zones) and the description offers nothing to route between them.

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