Skip to main content
Glama
pcb-agent-mcp

pcb-agent-mcp

unit_convert

Converts PCB measurement values between millimeters, centimeters, micrometers, nanometers, mils, thous, inches, and hundredths of an inch using a specified source and target unit.

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": {
      "value": "<value>",
      "from_unit": "<from_unit>",
      "to_unit": "<to_unit>"
    },
    "name": "unit_convert"
  }
}

Input Schema

NameRequiredDescriptionDefault
valueYes ...
to_unitYes ...
from_unitYes ...

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 disclosure burden and delivers none of it. It does not say whether the conversion is a pure computation, how rounding or precision is handled, based on which unit standard, or the shape of the result — all material facts for an agent deciding whether to call it.

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?

A single ellipsis is not conciseness but absence of content; there is no structure, no front-loaded statement of purpose, and no sentence that earns its place because no sentence exists. Any length here would be an improvement.

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?

For a 3-parameter, all-required tool with enum-constrained units and no output schema, the definition should at minimum describe the direction of conversion, the treatment of aliases such as thou/mil, and the return format. None of that is present, leaving the agent to guess at the tool's contract entirely.

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 reported at 100%, so the schema is nominally responsible for documenting value, from_unit and to_unit, which sets the baseline at 3 per the rubric. The description adds nothing beyond the schema, and it does not disambiguate the overlapping enum members (mil vs thou, inch vs in, 0.01inch vs 0.01in), which would have been the one place where prose could add real value.

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 states nothing about what the tool does. Any sense of purpose comes only from the tool name unit_convert, not from the definition text, and nothing distinguishes it from the many sibling calc_* and measurement tools.

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 exclusions, and no mention of any alternative tool. The agent must infer entirely on its own that this converts between length units rather than, say, applying design-rule calculations.

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