Skip to main content
Glama
pcb-agent-mcp

pcb-agent-mcp

calc_capabilities

Lists the calculation capabilities available in the PCB agent, showing which current-carrying, impedance, creepage, thermal, and magnetic-core calculators can be run.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.43

TDQS

D1.5/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 what a "capability" query returns, whether limits are reported per-unit or per-domain, or how results should be interpreted. An agent cannot predict the output of a call.

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 body is an empty placeholder rather than content, so there is nothing front-loaded and nothing that earns its place. Brevity here reflects absent information, not concision.

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 explaining what this tool returns, and it says nothing. Even for a simple zero-argument capability query, an agent needs to know the result shape (a list of supported checks, units, or limits) to use it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so the input schema is trivially complete and there is no parameter meaning for the description to add. Baseline 4 applies; the only gap is that the description could confirm the no-argument, capability-listing nature of the call.

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 " ..." — a placeholder that states no verb, resource, or purpose. Nothing distinguishes calc_capabilities from calculation-adjacent siblings such as current_capacity, ir_drop_chain, or clearance_required.

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 reference to any alternative tool. An agent has no basis for choosing this tool over the many domain-specific calculators in the sibling list.

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