Skip to main content
Glama
pcb-agent-mcp

pcb-agent-mcp

app_detect

Detects installed PCB design applications and returns their executable paths, helping the assistant select the correct KiCad, pcbnew, kicad-cli, or LCEDA Pro environment.

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": "app_detect"
  }
}

Input Schema

NameRequiredDescriptionDefault
appNo ...
explicit_pathNo ...

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 disclosure burden and delivers none of it. It does not say whether detection reads the filesystem, writes anything, requires a running editor instance, or how conflicts between app and explicit_path are resolved.

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?

There is no content to be concise about; the description is an unelaborated placeholder rather than a trimmed statement. Under-specification of this degree is not brevity.

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 zero annotations, no output schema, and an empty description, an agent has no behavioral picture of a detection tool whose result presumably drives downstream tool selection. The definition is functionally incomplete for the task it gates.

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 reported as 100% and the schema itself supplies the enum of accepted app values (lceda-pro, kicad, pcbnew, kicad-cli), so the structural contract is visible without the description. The description adds nothing, but with high coverage the baseline of 3 applies. The meaning of explicit_path and its interaction with app remain unexplained in prose.

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 (" ..."), containing no verb and no resource. Nothing states what app_detect detects or returns, so an agent cannot distinguish it from siblings such as app_status or lceda_pro_status on the basis of the definition.

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 mention of alternatives. The sibling list contains several plausibly overlapping tools (app_status, lceda_pro_status), yet the definition offers no routing signal at all.

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