Skip to main content
Glama
pcb-agent-mcp

pcb-agent-mcp

app_status

Check whether a supported PCB design application is running and reachable by probing its ports before using design, DRC, routing, or fabrication tools.

Instructions

...

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "app": "<app>"
    },
    "name": "app_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
appYes ...
probe_portsNo ...

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 disclosure burden and provides nothing. It does not say whether the call is read-only, whether it launches or mutates anything, whether it blocks on a probe, or what happens when the target app is not running.

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 body is a literal ellipsis with no substantive content, so the problem is under-specification rather than verbosity. There is nothing front-loaded and nothing for a reader to anchor 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?

With no annotations and no output schema, the description is the only channel for behavioral context, and it is empty. An agent has no information about what a status result contains or how probing behaves, which is inadequate even for a two-parameter tool.

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% and the single required parameter is an enumerated app identifier, so the schema alone documents the inputs. The description adds no meaning beyond that, but the high coverage sets the baseline 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 only the placeholder " ..." and never states what the tool does. An agent cannot tell from this whether app_status checks a running application, reports version info, or probes connectivity, nor how it differs from siblings such as app_detect or lceda_pro_status.

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 conditions, and no mention of alternatives. Given siblings named app_detect and lceda_pro_status, the absence of any routing guidance is a serious gap.

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