Skip to main content
Glama
pcb-agent-mcp

pcb-agent-mcp

schematic_pcb_diff

Compare schematic and PCB files to identify mismatches and keep design data synchronized before 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>",
      "schematic": "<schematic>"
    },
    "name": "schematic_pcb_diff"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYes ...
schematicYes ...

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 discloses nothing. Whether the tool reads files, mutates state, requires licensing or a running EDA process, and what it reports are all unstated.

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 short only because it is empty, not because it is efficient. There is no front-loaded purpose statement or structure to reward.

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 two-required-parameter diff tool with no annotations and no output schema depends entirely on the description, which is a placeholder. Nothing an agent needs in order to call this 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?

The schema nominally has 100% description coverage, but both path and schematic are documented only as " ...", so the coverage signal reflects placeholder text rather than real meaning. The description adds nothing to clarify what each parameter refers to (a file path? a project identifier? a schematic name?), leaving required-parameter semantics effectively undocumented.

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 " ..." and contains no verb, resource, or scope statement. Nothing distinguishes this from siblings such as schematic_pcb_sync, schematic_propose, or schematic_review, which all plausibly relate to schematic/PCB work.

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 named alternative. An agent cannot infer from the text whether this compares a saved schematic against a PCB, two files, or two revisions.

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