Skip to main content
Glama
pcb-agent-mcp

pcb-agent-mcp

lceda_pro_verify

Verifies a 立创 EDA Pro endpoint and session by running ping and probe checks with configurable timeouts, confirming the connection is ready before PCB operations.

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

Input Schema

NameRequiredDescriptionDefault
sessionNo ...
endpointNo ...
timeout_sNo ...
ping_timeout_sNo ...
probe_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 burden of behavioral disclosure and delivers nothing. It does not say whether verification is read-only, whether it starts or restarts a session, what side effects occur, or how long it may block given the timeout parameters.

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?

A single placeholder token is not concise, it is absent. There is no front-loaded purpose statement or structure for an agent to parse.

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?

For a tool with five parameters and three separate timeout knobs, an unannotated mutating-sounding operation needs far more than an empty string. No output schema exists to compensate, so an agent cannot predict inputs, behavior, or results.

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 technically lists five typed parameters with defaults (timeout_s=10, ping_timeout_s=3, probe_timeout_s=15), but each description is an empty " ..." placeholder, so the stated 100% coverage is nominal only. Only the parameter names and defaults convey any meaning; the description adds nothing about session, endpoint, or the three distinct timeouts.

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 literal placeholder string " ..." with no verb, resource, or scope. Nothing states what lceda_pro_verify verifies, and the name alone does not distinguish it from siblings like lceda_pro_status or lceda_pro_recover.

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 prerequisites, and no indication of which sibling to pick instead (open, status, recover, close_extra). An agent has no basis for selecting this tool over the others.

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