Skip to main content
Glama
pcb-agent-mcp

pcb-agent-mcp

epro_inspect

Inspect a 立创 EDA Pro project file to extract PCB design details and component data, using a configurable sample count for focused review.

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": {
      "path": "<path>"
    },
    "name": "epro_inspect"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYes ...
sampleNo ...

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 provided, so the description carries the full burden of behavioral disclosure, and it discloses nothing: not whether inspection is read-only, how paths are resolved, what limits apply, or what the inspection produces. For a tool with zero annotation coverage this is a total gap.

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 description is not concise, it is absent - an unfilled placeholder (" ... ") rather than a front-loaded summary. Nothing is structured or front-loaded because no content exists; this is under-specification, 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?

Given 2 parameters, no annotations, and no output schema, the description is the only channel for explaining behavior and it is empty. An agent has no way to know what inspecting a path returns or how the sample parameter affects results.

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 both the path and sample parameters are already documented in the input schema, which sets the baseline at 3. The description adds no meaning beyond the schema, but by the stated rubric the schema's own coverage prevents a lower score.

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 placeholder string (" ... ") that conveys nothing. The tool name epro_inspect suggests some kind of inspection of an "epro" resource, but no verb, resource, or scope is actually stated, so an agent cannot distinguish it from siblings such as board_summary or part_get.

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 any alternative tool. With a name that could mean anything from file inspection to netlist inspection, the agent has no basis for selecting this tool over the many board_* and part_* siblings.

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