Skip to main content
Glama
pcb-agent-mcp

pcb-agent-mcp

lambda_over_20

Calculates the λ/20 wavelength length at a given frequency and dielectric constant for PCB trace spacing and layout checks.

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": {
      "freq_ghz": "<freq_ghz>"
    },
    "name": "lambda_over_20"
  }
}

Input Schema

NameRequiredDescriptionDefault
erNo ...
divisorNo ...
freq_ghzYes ...

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 provided, so the description carries the full disclosure burden, and it discloses nothing. It does not say whether values are computed locally, what units or conventions apply, or what the result represents.

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?

There is nothing to be verbose about, but the empty placeholder is under-specification rather than concise phrasing. Nothing is front-loaded because there is no content.

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?

This is a computational tool with a required input, two defaulted inputs, and no output schema, so the description is the only place to explain the calculation. It provides none of that, leaving the tool effectively opaque.

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% for all three parameters (er, divisor, freq_ghz), so the schema already documents their meaning and defaults; the description adds no parameter insight, which matches the baseline 3 for fully documented schemas. No penalty is applied since the schema does the heavy lifting, but no credit is earned either.

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 literal placeholder (" ...") and conveys no purpose at all. The name lambda_over_20 hints at a wavelength calculation, but nothing states the verb, resource, or result, so an agent cannot distinguish it from siblings like current_capacity or diff_impedance.

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. The agent must guess the tool's role from its name alone.

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