Skip to main content
Glama
pcb-agent-mcp

pcb-agent-mcp

board_components

Lists components on a PCB design from a KiCad or 立创 EDA project, with optional layer filtering and pagination to inspect board parts.

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

Input Schema

NameRequiredDescriptionDefault
pathYes ...
layerNo ...
limitNo ...
memberNo ...
offsetNo ...
projectNo ...

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 disclosure and delivers nothing. It does not say whether this is a read-only listing, whether it hits a live board or a file, what happens with an invalid path, or anything about pagination despite limit/offset parameters.

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?

This is not conciseness but absence — the single ellipsis token conveys no information and is not front-loaded with anything. There is no 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?

A six-parameter tool with no annotations and no output schema depends entirely on the description for behavioral context, and the description is empty. Even with a documented schema, the agent cannot tell what the tool returns or how paginated results behave.

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?

Reported schema description coverage is 100%, so the six parameters are documented in the schema itself and the baseline of 3 applies regardless of the empty description. The text adds no meaning beyond the schema, but it is not required to when coverage is complete (note: the visible schema description strings are elided placeholders).

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 (" ..."), so it states no verb and no resource. Any sense of purpose comes only from the tool name 'board_components', which the description does not corroborate or clarify.

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 text at all, so no when-to-use, when-not-to-use, or alternative is named. With siblings like board_nets, board_view, and board_summary in the same family, the agent is left to guess which one retrieves component data.

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