Skip to main content
Glama
pcb-agent-mcp

pcb-agent-mcp

lceda_pro_open

Open an LCEDA Pro project or design file by path to inspect or edit PCB and schematic content, with controls for headless launch, wait time, timeout, and app upgrades.

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

Input Schema

NameRequiredDescriptionDefault
pathYes ...
forceNo ...
wait_sNo ...
canary_sNo ...
endpointNo ...
headlessNo ...
timeout_sNo ...
keep_windowNo ...
allow_upgradeNo ...
open_timeout_sNo ...

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.43

TDQS

D1.4/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 about what launching the application does, whether it spawns a GUI process, whether it can upgrade the install (allow_upgrade parameter), or what side effects persist after the call. Params like force, canary_s, keep_window, and headless imply meaningful side effects that go entirely unaddressed in prose.

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 description is a stub, so there is nothing superfluous but also nothing front-loaded or structured. This is under-specification rather than conciseness, which prevents any useful scanning by an agent.

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?

This is a ten-parameter application-launch tool with no annotations and no output schema, which is precisely the case where the description must do the most work. Instead it says nothing about startup behavior, failure modes, process lifetime, or return values, leaving the definition materially inadequate for correct invocation.

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 100%, so each of the ten parameters is documented in the schema itself and the description need not repeat it. The baseline of 3 applies, though the description adds no cross-parameter guidance such as how wait_s, canary_s, timeout_s, and open_timeout_s interact.

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 (" ...") and the title is null, so the only signal about purpose is the tool name lceda_pro_open. An agent must infer from the name alone that this opens an LCEDA Pro project, and nothing distinguishes it from siblings such as lceda_pro_recover, lceda_pro_verify, or lceda_pro_status.

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 text at all indicating when to use this tool versus lceda_pro_recover, lceda_pro_status, or lceda_pro_close_extra, nor any stated prerequisites such as whether the application must be installed or already running. No exclusions or alternative routing are provided.

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