Skip to main content
Glama
pcb-agent-mcp

pcb-agent-mcp

tool_call

Invoke a named PCB design tool on the pcb-agent-mcp server by passing its name and arguments. Use it to trigger calculations, DRC, or KiCad and 立创 EDA Pro actions from one call.

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": {
      "name": "<name>"
    },
    "name": "tool_call"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes ...
argumentsNo ...

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 behavioral burden, and it discloses nothing: not whether the invoked tool is read-only or destructive, not what happens on failure, not whether arguments are validated or forwarded verbatim. For a generic dispatch tool this is the most critical missing information.

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?

There is nothing to trim, but the definition is under-specified rather than concise; an empty string earns no credit for structure or front-loading. It fails the 'every sentence should earn its place' test by having no sentence at all.

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?

The tool takes a required name plus a nested arguments object, has no annotations and no output schema, so the description must explain dispatch semantics, naming expectations, and return behavior. It does none of that, leaving the definition unusable without external knowledge.

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 visible field descriptions are the same " ..." placeholders, so no real semantics are conveyed in structured or prose form. The nested "arguments" object is especially consequential for a generic dispatcher (what shape does it take? does it need to match the target tool's schema?) and the description explains none of it.

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 string (" ..."), so the only signal about purpose is the name "tool_call", which merely restates that a tool is being invoked. There is no verb/resource statement and nothing distinguishes it from siblings such as tool_search or part_get.

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 mention of any alternative tool. An agent has no way to know whether to call tool_call, tool_search, or a domain-specific sibling like app_detect or board_create.

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