Skip to main content
Glama
pcb-agent-mcp

pcb-agent-mcp

lceda_pro_close_extra

Close extra LCEDA Pro windows or dialogs to reduce clutter and keep the PCB design workspace focused, with optional confirmation and wait time.

Instructions

...

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "lceda_pro_close_extra"
  }
}

Input Schema

NameRequiredDescriptionDefault
wait_sNo ...
confirmNo ...
keep_hwndNo ...

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 behavioral burden, and it discloses nothing. For a 'close' operation an agent needs to know what state is destroyed, whether unsaved work is lost, whether a confirmation prompt appears, and whether the call blocks — none of which is stated.

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 not concise, it is absent: a single ellipsis with no front-loaded statement of action. There is no structure to evaluate and nothing 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 three-parameter mutating tool with no annotations and no output schema requires the description to explain behavior and outcomes. It is entirely missing, leaving the agent unable to judge safety, side effects, or return behavior.

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 reported as 100%, which would normally set a baseline of 3, but the supplied schema descriptions for wait_s, confirm, and keep_hwnd are themselves ellipsis placeholders (' ...'), so no actual meaning is conveyed anywhere. The description adds nothing about units, semantics of keep_hwnd, or what confirm gates.

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 field contains only the placeholder string '" ..."' and the title is null, so there is no stated verb, resource, or scope. An agent can only guess from the name that this closes something called 'extra' in the lceda_pro family, which is not a usable purpose statement.

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 on when to call this tool, when not to, or how it relates to siblings such as lceda_pro_open, lceda_pro_status, or lceda_pro_recover. Nothing indicates whether it is a cleanup step, a forced-close escape hatch, or a routine shutdown.

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