Skip to main content
Glama
pcb-agent-mcp

pcb-agent-mcp

lceda_pro_projects

List and inspect LCEDA Pro projects across project, recovery, and online-backup sources to find the design you need before opening or editing it.

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

Input Schema

NameRequiredDescriptionDefault
deepNo ...
limitNo ...
sourceNo ...
ask_editorNo ...
ping_timeout_sNo ...
probe_timeout_sNo ...

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.43

TDQS

D1.3/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 discloses nothing. Whether this is a read-only probe, whether it touches recovery or online-backup state, and what side effects the ask_editor or ping options produce are all unstated.

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 definition is not concise but absent — a single ellipsis carries no front-loaded purpose, no structure, and no content an agent can act on.

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 six-parameter tool with an enum-typed source selector, no annotations, and no output schema needs a real description to be callable correctly. Nothing is provided, leaving the agent to guess at behavior entirely from the schema.

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 the six parameters (including the source enum and the timeout fields) are already documented in the schema. The description contributes no additional parameter meaning, but per the high-coverage baseline the schema alone keeps this at 3.

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 (' ...') that states nothing about what lceda_pro_projects does. The name alone suggests project listing, but no verb, resource scope, or distinction from siblings like lceda_pro_status or lceda_pro_recover is provided.

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 use this tool, when not to, or which sibling (lceda_pro_open, lceda_pro_recover, lceda_pro_status) it should be preferred over. The agent has nothing to route on.

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