Skip to main content
Glama
pcb-agent-mcp

pcb-agent-mcp

lceda_pro_recover

Recover access to 立创 EDA Pro by reconnecting or restoring the design session after an interruption or failed connection.

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_recover"
  }
}

Input Schema

NameRequiredDescriptionDefault
wait_sNo ...
confirmNo ...
ping_timeout_sNo ...

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 supplied, so the description carries the full behavioral burden and discharges none of it. It does not say whether recovery is destructive to existing state, whether it requires the app to be closed or verified first, what 'confirm' actually authorizes, or what a failed recovery looks like — for an operation named 'recover' these are exactly the facts that matter.

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 absence: the description field contains no content at all, so there is nothing front-loaded and no structure to assess. Every sentence that should exist is missing rather than trimmed.

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, zero-required recovery tool with no annotations and no output schema depends entirely on prose that does not exist. The agent has no way to know what the tool returns, what defaults imply, or when invoking it could damage the user's work.

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 schema nominally reports 100% description coverage, but every parameter description is itself the placeholder ' ...', so no meaning is actually conveyed for wait_s, confirm, or ping_timeout_s. The description says nothing about them either, leaving the agent to guess units, whether confirm=true is required to proceed, and how the timeouts 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 is the name 'lceda_pro_recover'. Nothing states what is being recovered (session, autosave, project, lock) or how it differs from siblings like lceda_pro_open, lceda_pro_status, or lceda_pro_verify.

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 preconditions, and no mention of alternatives. An agent cannot tell whether recovery is a routine open-path step, a crash-recovery action, or something to avoid when a project is already open.

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