Skip to main content
Glama
pcb-agent-mcp

pcb-agent-mcp

schematic_review

Review schematic facts to catch design issues and confirm circuit intent before layout, DRC, 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": {
      "facts": "<facts>"
    },
    "name": "schematic_review"
  }
}

Input Schema

NameRequiredDescriptionDefault
factsYes ...

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 disclosure, and it discloses nothing: not whether the tool reads or mutates, what it touches, what permissions it needs, or what it returns. The name implies a review/read, but that is inference from the name, not evidence.

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?

This is not conciseness but an empty placeholder; there is no content to be front-loaded and 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?

A nested-object parameter with no annotations and no output schema demands substantial descriptive context, and the definition supplies none. An agent cannot reliably construct the 'facts' payload or predict the effect of calling it.

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 single required parameter 'facts' is a nested object whose own description is also a " ..." placeholder, so the reported 100% schema coverage is nominal rather than substantive. The description adds no meaning about what a 'facts' object must contain or how it is structured.

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 " ...", which conveys no verb, no resource, and no scope. Nothing distinguishes it from siblings such as schematic_propose or schematic_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 exclusion of alternatives, and no stated prerequisites. An agent has no basis to choose this tool over the many schematic_* and board_* siblings.

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