Skip to main content
Glama
pcb-agent-mcp

pcb-agent-mcp

board_rules_write

Writes design rules into a PCB board file by applying a list of rule operations to a given path, with an optional dry run to preview changes before saving.

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

Input Schema

NameRequiredDescriptionDefault
pathYes ...
dry_runNo ...
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 disclosure burden, and it is empty. Nothing states that this mutates project files, what a write overwrites, whether it is reversible, or whether dry_run mitigates risk.

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 placeholder text has no structure, no front-loaded summary, and conveys zero information. This is under-specification rather than conciseness, leaving no sentence that earns its place.

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 write tool with no annotations, no output schema, and a nested-array operations parameter, so it needs substantial behavioral and sequencing detail. The definition supplies none, making it inadequate for an agent to invoke safely.

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 path, operations, and dry_run are already documented in the schema; the baseline applies. The description adds nothing extra about operation object shapes or path scoping, but the schema does 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 an empty placeholder (" ..."), so the only signal about purpose comes from the tool name board_rules_write. Nothing states what resource is written, in what format, or how it differs from siblings such as board_rules or board_apply.

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 prerequisite or ordering hint, and no mention of alternatives like board_rules (read) or board_propose. An agent has to guess whether writing rules must follow reading or precede board_apply.

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