Skip to main content
Glama
pcb-agent-mcp

pcb-agent-mcp

board_zones

Lists PCB copper zones and their properties from a board file, so you can inspect pours, boundaries, and net assignments.

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

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.43

TDQS

D1.2/5.0
Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full burden of behavioral disclosure, and it is empty. It does not say whether the tool is read-only or mutating, what permissions it needs, what it returns, or what happens with an unknown path.

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 text is technically short but is placeholder filler rather than concise writing; it has no front-loaded purpose statement and no structure an agent can parse. Brevity here reflects under-specification, not economy.

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 no annotations and no output schema needs the description to explain behavior and results, and it explains neither. Nothing an agent needs in order to invoke board_zones correctly is present.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is nominally 100%, but the per-parameter descriptions are themselves placeholders (" ..."), so the schema conveys only names and types. The description adds nothing about what path/member/project mean, how they interact, or which combinations are valid, leaving meaning to be guessed from the parameter names alone.

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 literal placeholder " ...", so it states no verb, resource, or outcome. An agent cannot tell from the text whether board_zones lists zones, creates them, or validates geometry; only the bare tool name hints at a board/zone association.

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 indication of how this differs from siblings such as board_rules, board_components, or board_summary. The description offers nothing to route on.

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