Skip to main content
Glama
pcb-agent-mcp

pcb-agent-mcp

schematic_summary

Summarize a schematic file to extract key components, nets, and connectivity, enabling quick design review without manual inspection.

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": "schematic_summary"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYes ...
engineNo ...

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 burden of behavioral disclosure and delivers nothing. It does not state whether the call is read-only, what it parses, what happens on a missing or malformed file, or what the result contains.

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 description is a placeholder rather than prose, so there is no structure, no front-loaded purpose, and nothing that earns its place. This is under-specification, not conciseness.

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-parameter tool with no annotations and no output schema depends entirely on the description to explain its return value and the meaning of the 'engine' flag. The definition supplies none of that, leaving the tool effectively undocumented.

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 reported at 100% with only two parameters (path required, engine boolean defaulting to true), so the structured schema itself is the documented source of parameter meaning. The description contributes nothing beyond that, which is the baseline case rather than a strength.

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 a placeholder string of " ..." and states nothing about what the tool does. Only the name 'schematic_summary' hints at returning a summary of a schematic, which is inference, not documentation. It does not distinguish this from siblings such as board_summary or schematic_review.

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 guidance at all on when to use this tool, when not to, or which sibling to pick instead. An agent cannot tell from the definition whether this is the right entry point versus board_summary or schematic_review.

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