Skip to main content
Glama
pcb-agent-mcp

pcb-agent-mcp

board_create

Creates a PCB board file at a specified path using dimensions, origin, thickness, and copper-layer settings, with optional title and overwrite control.

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

Input Schema

NameRequiredDescriptionDefault
pathYes ...
specNo ...

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 full disclosure burden, and it discloses nothing. It does not state that this is a mutating/creating operation, whether an existing board at path is replaced, what overwrite (defaulting to false) implies, or what permissions or side effects are involved.

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?

The text is trivially short because it is empty rather than because it is efficient. There is no front-loaded statement of purpose or any structure to speak of, which is under-specification rather than 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?

This is a creation tool with a nested spec object, no annotations, and no output schema, so the description must supply behavioral context and supplies none. An agent cannot tell what a successful call returns, whether the board file is new or replaced, or what default geometry means.

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%, including the nested spec object, so the schema itself documents path, title, origin, dimensions, thickness, copper layers, and overwrite. Per the high-coverage baseline this scores 3, though the description adds no interpretation such as unit conventions or the interaction between path and spec.title.

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 conveys no verb, resource, or scope beyond what the bare name board_create suggests. It does not distinguish this tool from siblings like board_apply or board_propose, and an agent gets no confirmation of what is actually created.

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 exclusions, and no mention of alternatives among the many board_* siblings. The description provides nothing to help an agent decide between board_create and board_propose or board_apply.

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