Skip to main content
Glama
pcb-agent-mcp

pcb-agent-mcp

lceda_pro_status

Checks an LCEDA Pro endpoint's availability and response status to verify PCB design integration before running design or fabrication tasks.

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

Input Schema

NameRequiredDescriptionDefault
endpointNo ...
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 burden of behavioral disclosure, and it provides none. It does not say whether the call is read-only, whether it starts or probes a process, how long it may block, or what happens on timeout, despite a timeout_s parameter implying a blocking operation.

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 single placeholder line wastes no words but conveys no content; this is severe under-specification rather than concision. There is no front-loaded purpose statement to structure the rest around.

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?

With no annotations and no output schema, the definition offers an agent nothing to reason about: no return shape, no side effects, no failure modes. For a tool that presumably probes status and accepts a timeout, this is entirely inadequate.

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?

Per the stated rule, schema description coverage is 100%, so the schema is the source of truth for the two parameters and the baseline is 3. However, the description adds no meaning whatsoever about endpoint or timeout_s beyond what the schema declares.

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 (' ...') with no verb, resource, or scope stated. The tool name lceda_pro_status suggests a status query for the LCEDA Pro tool/application, but nothing in the description confirms this or distinguishes it from siblings such as app_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?

No when-to-use guidance, no prerequisites, and no mention of alternatives are provided. An agent has no basis for choosing this over app_status or lceda_pro_verify.

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