On the Register

calc_reconstitute

Work out the units to draw for a prescribed dose from a powder vial and bacteriostatic water. Inputs: vial mg, water mL, the dose (mg or mcg), and the syringe. Returns units, mL, the nearest syringe line and doses per vial. Arithmetic only — the user's own dose, no presets.

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>"
    },
    "name": "calc_reconstitute"
  }
}

Input Schema

Name	Required	Description	Default
`dose`	Yes	The prescribed dose, in the unit given by dose_unit
`syringe`	No		u100-0.5
`vial_mg`	Yes	Powder in the vial, in mg
`water_ml`	Yes	Bacteriostatic water added, in mL
`dose_unit`	No		mcg

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 7, 2026

TDQS

A4.2/5.0

Behavior4/5

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

With no annotations, the description carries the full load, and it does disclose the concrete return contents (units, mL, nearest syringe line, doses per vial) and that the operation is pure arithmetic with no presets or stored data. It stops short of describing edge-case behavior, such as what happens when the dose exceeds the vial's capacity or when syringe graduation makes an exact draw impossible.

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 dense sentences, front-loaded with the purpose, then inputs, then outputs, then the arithmetic-only caveat. No filler or repetition of the tool name.

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?

There is no output schema, but the description enumerates the return values, so an agent knows what to expect, and all five inputs are at least mentioned. Remaining gaps are edge-case and error behavior for a calculation that can produce impossible draws.

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 60%, leaving the syringe and dose_unit properties largely undocumented; the description compensates by naming the syringe as an input and clarifying the dose may be in mg or mcg. It still does not explain the syringe size options or the default, so it adds meaning but not fully.

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?

"Work out the units to draw for a prescribed dose from a powder vial and bacteriostatic water" names a specific verb (work out units to draw) and the exact resource context (powder vial + bacteriostatic water). This clearly separates it from arithmetic siblings like calc_convert or bmi_check, which do not involve reconstitution math.

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?

"Arithmetic only — the user's own dose, no presets" sets a useful scope boundary, implying it is used for a single user-supplied dose rather than stored protocols. However, it never names an alternative sibling (e.g., calc_convert for plain unit math, pen_howto for injection technique) or states when not to use it.

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

All On the Register tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?