Skip to main content
Glama
PeptaraLabs

Reconstitution Calculator MCP Server

by PeptaraLabs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

Convert units

convert_units
Read-onlyIdempotent

Convert laboratory values between mass, volume, or mass concentration units such as mg, mL, and mg/mL for accurate dilution and dosing calculations.

Instructions

Convert a value between units of the same kind: mass, volume or mass concentration. Supported units: kg, g, mg, mcg, ug, µg, ng, L, mL, uL, µL, nL, g/L, mg/mL, mg/L, mcg/mL, ug/mL, µg/mL, mcg/L, ug/L, µg/L, ng/mL. For laboratory calculations only.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
toYesUnit to convert to, of the same kind as from.
fromYesUnit to convert from, for example mg, mL or mg/mL.
valueYesValue to convert.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.5/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already establish that this is read-only, idempotent, non-destructive, and closed-world. The description adds useful behavioral context by restricting conversions to matching unit kinds and limiting use to laboratory calculations, though it does not describe error behavior for incompatible units.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The conversion purpose is front-loaded, followed by the necessary supported-unit list and a brief scope restriction. The long unit enumeration is functional and earns its space.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple three-parameter, read-only conversion tool with no output schema, the description supplies everything needed to invoke it correctly: supported unit kinds, exact unit tokens, and the laboratory-use restriction.

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?

Schema coverage is 100%, so the baseline is 3. The description meaningfully extends the schema by enumerating all supported units—including equivalent spellings like ug/µg and uL/µL—which the schema itself does not list.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (Convert) and resource (a value between units), and scopes it to mass, volume, and mass concentration. The explicit supported-unit list makes it clearly distinguishable from sibling calculation tools like molarity or serial_dilution.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives clear context: conversions must be between units of the same kind and are for laboratory calculations only. It does not explicitly compare to sibling tools, but those are different calculation types rather than alternatives for unit conversion.

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

Deploy Server

Other Tools