Skip to main content
Glama
pcb-agent-mcp

pcb-agent-mcp

board_summary

Summarizes a PCB design file or project board, returning key metrics and structure for quick review and verification.

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

Input Schema

NameRequiredDescriptionDefault
pathYes ...
memberNo ...
projectNo ...

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.43

TDQS

D1.4/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 entire burden of behavioral disclosure, and it discloses nothing. Whether this reads or mutates the board, what permissions or open-document state it needs, and whether it is expensive or cached are all unknown. Given a name like board_summary plus siblings such as board_apply and board_create, an agent has no basis to judge safety.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

There is nothing to trim, but the problem is under-specification rather than brevity: the field holds only a placeholder ellipsis. It is not front-loaded with any information because it contains none.

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 three-parameter tool with one required argument, no annotations and no output schema needs the description to explain scope and return shape, and it explains neither. The definition is completely inadequate for the tool's complexity.

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 schema nominally documents path, member and project, and the baseline of 3 applies. The description adds no meaning at all about what those values select or how they interact, so it neither helps nor misleads beyond the schema.

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 an empty placeholder (" ...") and provides no verb, resource, or scope. An agent cannot tell from this text what board_summary does or how it differs from schematic_summary, board_view, or board_components.

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. The sibling list contains schematic_summary and board_view, but the definition gives nothing to distinguish this tool from them.

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