Skip to main content
Glama
pcb-agent-mcp

pcb-agent-mcp

board_propose

Proposes and applies PCB board edits by validating requested operations, running DRC and layer-policy checks, and writing changes in place or to a new KiCad file.

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>",
      "operations": "<operations>"
    },
    "name": "board_propose"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYes ...
optionsNo ...
operationsYes ...

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 behavioral disclosure and delivers nothing. It does not say whether the tool mutates the file in place, produces a proposal for later application, requires a license or project to be open, or how failures are surfaced.

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?

There is no content to be concise about — the entire description is an unfilled placeholder. This is under-specification rather than efficient brevity.

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 complex, high-risk tool: a required file path, an operations array of free-form objects, and a deep options object with safety-gating flags like allow_new_violations and strict_drc. With no annotations and no output schema, the empty description leaves an agent with nothing to reason about before invoking a mutating board operation.

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 reported at 100% and the schema enumerates the nested options (mode, engine, strict_drc, allow_* flags, precheck_layer_policy), so the structured data nominally documents the parameters. The description adds no meaning beyond it; baseline 3 applies because the schema, not the prose, is doing the work.

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 literal placeholder (' ...') and states no verb, resource, or scope. An agent cannot tell from the definition what board_propose actually does or how it differs from board_apply, board_create, or schematic_propose.

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 such as board_apply. Any routing decision would have to be guessed from the name alone.

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