Skip to main content
Glama
pcb-agent-mcp

pcb-agent-mcp

board_rules

Extract PCB design rules from a project path to review constraints before routing, DRC checks, or fabrication.

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

Input Schema

NameRequiredDescriptionDefault
pathYes ...

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 discloses nothing — not whether the tool is read-only, what 'path' refers to, what happens on an invalid path, or whether any state is mutated. The name alone leaves the read/write question genuinely ambiguous given a sibling named board_rules_write.

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 structure; the placeholder text conveys zero information and is not front-loaded with anything usable.

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?

For a required-path tool with no annotations and no output schema, the description should at minimum explain what the path points to and what the tool returns. None of that is present, so the definition is unusable as written.

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 coverage is nominally 100%, but the single parameter's schema description is also a '...' placeholder, so the parameter's meaning is undocumented in both places. The description adds no semantics for 'path' — whether it is a board file, a project directory, or a rules file — leaving the nominal coverage empty of value.

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 string '" ..."' — a placeholder with no verb, resource, or scope. Nothing distinguishes board_rules from siblings such as board_rules_write, board_drc, or board_summary.

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 reference to alternatives. An agent cannot infer from the definition whether this reads design rules, validates them, or writes them (the sibling board_rules_write suggests a meaningful distinction that is never stated).

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