Skip to main content
Glama

Solution prep (molarity and C1V1)

solution_prep
Read-onlyIdempotent

Use when someone asks how much solid to weigh for a molar solution (how many grams for X mM in Y mL, making up a buffer or salt solution), or how much stock to dilute to a target concentration (C1V1). mode "solid": mass of solid to weigh from molecular weight, target concentration and final volume. mode "stock": C1V1 = C2V2 dilution from a stock, solving for stockVolume, stockConcentration, targetConcentration or finalVolume. Returns the primary result, a step summary, warnings and safety notes.

Input Schema

NameRequiredDescriptionDefault
modeNoUse solid to calculate mass from molecular weight, or stock for C1V1 dilution.
solventNoSolvent or diluent to include in the preparation note.
solveForNoFor stock mode, choose which C1V1 variable to solve.
finalVolumeNoV2 final preparation volume.
stockVolumeNoV1 stock volume.
solutionNameNoName for the solution being prepared.
finalVolumeUnitNo
molecularWeightNoMolecular weight in g/mol. Required when mode is solid.
stockVolumeUnitNo
stockConcentrationNoC1 starting stock concentration.
targetConcentrationNoC2 final or desired target concentration.
stockConcentrationUnitNo
targetConcentrationUnitNo

Output Schema

NameRequiredDescriptionDefault
cardNoWhat the Verbex card draws; same values as the notebook entry.
toolYes
resultNo
humanUrlNo
warningsNo
inputNotesNoHow the input was read when it was not in the documented shape. Tell the user.
safetyNotesNo
toolVersionNo
notebookEntryNoMarkdown entry to paste into a lab notebook.
validationErrorsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedOutput schema / properties / inputNotes
      Added value: +{
      +  "description": "How the input was read when it was not in the documented shape. Tell the user.",
      +  "items": {
      +    "type": "string"
      +  },
      +  "type": "array"
      +}
  2. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already establish that this is a safe, read-only, idempotent calculation. The description adds useful behavioral context by saying it returns the primary result, a step summary, warnings, and safety notes. It does not discuss error behavior or unit-mismatch handling, which would matter for a computational tool.

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 description is front-loaded with the usage trigger, followed by mode-specific behavior and return contents. It is dense but every sentence carries information, and there is no redundant or filler text.

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?

For a 13-parameter, conditionally structured calculation tool with an output schema, the description covers purpose, mode selection, core inputs, and return shape. The notable gap is that it does not address unit consistency or validation behavior, which are relevant for correct invocation.

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?

The description adds real meaning beyond the schema by explaining what inputs each mode requires and by enumerating the four C1V1 variables that solveFor can target. With 69% schema description coverage, some unit parameters remain unexplained in both places, so the semantic picture is not complete.

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

Purpose4/5

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

The description states a specific calculation purpose: mass of solid to weigh for a molar solution or stock dilution via C1V1. It clearly distinguishes the two modes and the variables solved, but it never names or contrasts a sibling tool such as serial_dilution, leaving sibling differentiation implicit.

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?

It explicitly opens with 'Use when someone asks how much solid to weigh...' and 'how much stock to dilute...', giving a clear triggering context for each mode. It does not state when not to use the tool or name an alternative calculator, so it falls short of full routing guidance.

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