Skip to main content
Glama
pcb-agent-mcp

pcb-agent-mcp

board_nets

Lists electrical nets from a PCB board file with pagination and optional member filtering for connectivity inspection and validation.

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

Input Schema

NameRequiredDescriptionDefault
pathYes ...
limitNo ...
memberNo ...
offsetNo ...
projectNo ...

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. It does not say whether the tool is read-only, what it returns, whether it queries a live board or a file on disk, or what happens with an invalid path.

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 an ellipsis placeholder rather than content — this is under-specification, not conciseness. There is no front-loaded statement of purpose to anchor the agent.

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 five-parameter tool with no annotations and no output schema needs a substantial description to explain behavior and results. The definition supplies none, leaving the agent entirely dependent on the schema field descriptions for parameters and on guesswork for everything else.

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 all five parameters (path, limit, member, offset, project) are documented within the schema itself. Per the high-coverage baseline this scores a 3 even though the description adds no meaning of its own.

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 (' ...') with no verb, resource, or scope. An agent can only guess from the tool name 'board_nets' that it relates to PCB net listing, and cannot distinguish it from siblings like board_summary or board_components.

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 reference to alternatives such as board_summary or board_view. Nothing tells the agent when this tool is the right choice over its 30-plus siblings.

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