Skip to main content
Glama

PepVault

Reconstitution arithmetic

reconstitution
Read-onlyIdempotent

Work out a mixed vial's strength, the units to read on a U-100 insulin syringe for a given amount, and how many doses the vial holds, from the vial's mg, the water's mL and the amount. Arithmetic on the numbers given, the same math as PepVault's calculator, not a dose recommendation.

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": {
      "vial_mg": "<vial_mg>",
      "water_ml": "<water_ml>",
      "dose": "<dose>",
      "dose_unit": "<dose_unit>"
    },
    "name": "reconstitution"
  }
}

Input Schema

NameRequiredDescriptionDefault
doseYesThe amount to draw, in dose_unit.
vial_mgYesThe vial's amount of powder, in mg.
compoundNoThe compound in the vial, to link its vial chart.
water_mlYesThe water added, in mL.
dose_unitYesThe unit of dose.
syringe_mlNoThe U-100 insulin syringe's size in mL (0.3, 0.5 or 1), to check the amount fits.

Output Schema

NameRequiredDescriptionDefault
doseYes
noteYes
vial_mgYes
water_mlYes
dose_unitYes
volume_mlYes
syringe_mlNo
units_u100Yes
fits_syringeNo
calculator_urlYes
doses_per_vialYes
vial_chart_urlYes
strength_mg_per_mlYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive behavior; the description adds that this is pure arithmetic matching a calculator and not medical advice. That extra safety framing is useful, though it does not discuss error cases or output behavior beyond what the output schema supplies.

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?

Two tight sentences with the core computation front-loaded and the safety caveat placed at the end. No wasted wording.

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

Completeness4/5

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

Given a full input schema, an output schema, and annotations, the description covers the essential purpose and the arithmetic-only boundary. It could mention the optional compound link or syringe-size check, but those are adequately covered by the schema.

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 the input parameters are already well documented. The description restates the main inputs (vial mg, water mL, amount) but adds little semantic detail beyond the schema, leaving optional compound and syringe_ml handling to the schema.

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 ('work out') and three concrete computed outputs: mixed vial strength, U-100 syringe units, and dose count. It also explicitly distinguishes itself from a dose recommendation, which separates it from reference-style siblings like get_dose_reference.

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

Usage Guidelines3/5

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

Implies usage when the vial mg, water mL, and amount are known, and says it is arithmetic rather than a dose recommendation. However, it does not name an alternative tool or state prerequisites explicitly, so routing still requires inference.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources