Skip to main content
Glama
omnioperand-mcp

omnioperand-mcp

omni_molarity_normality_solution

Calculate solute mass in grams and solution normality for preparing defined molarity, volume, and molecular-weight lab solutions, avoiding manual formula errors.

Instructions

Solution Molarity, Molality & Normality Preparation Calculator. Calculate chemical solute mass required in grams to prepare precise laboratory solutions of defined Molarity (M), Normality (N), and target volume. Discipline: BIOTECH. Governing mathematical model / formula: Solute Mass (g) = Molarity (mol/L) · Volume (L) · Molecular Weight (g/mol) | Normality = Molarity · Valence (eq/mol).

USAGE GUIDELINES:

  • WHEN TO USE: Invoke for deterministic calculation of required_solute_mass_grams (Solute Mass to Weigh on Balance), solution_normality_n (Solution Normality (N)), total_moles_dissolved (Total Dissolved Moles), solution_mass_percentage (Approximate Weight/Volume (w/v %)) using target_molarity_mol_l (Desired Target Molarity (M in mol/L) in M), solution_volume_liters (Target Solution Volume (Liters) in L), molecular_weight_g_mol (Solute Formula Weight / MW (g/mol) in g/mol), solute_valence_factor (Valence Factor (Equivalents per Mole) in eq/mol). Guarantees exact machine floating-point precision, eliminating LLM arithmetic mistakes and formula hallucinations.

  • WHEN NOT TO USE: Do not use for qualitative evaluations or unquantified reasoning. All input parameters must be valid numerical values.

  • SIBLING ROUTING: Use this dedicated specialist tool for 'Solution Molarity, Molality & Normality Preparation Calculator' rather than generic dispatchers like omni_universal_query. For cross-discipline dynamic dispatch, see omni_universal_query.

BEHAVIOR & SAFETY:

  • Pure deterministic computation with machine floating-point precision.

  • Read-only, idempotent, and stateless. Zero side effects or persistent state mutations.

  • Input validation: All arguments are validated against physical and domain bounds. Out-of-bounds inputs return a safe diagnostic error status without throwing runtime exceptions.

RETURNS:

  • Structured JSON object containing:

    • status (string): "success" on valid execution or "error" if validation fails

    • calculator (string): "molarity-normality-solution"

    • category (string): "biotech"

    • name (string): "Solution Molarity, Molality & Normality Preparation Calculator"

    • formula (string): Governing mathematical formula string

    • inputs (object): Echoed input parameter dictionary with applied defaults

    • metrics (object): Dictionary of computed outputs:

      • metrics.required_solute_mass_grams (Solute Mass to Weigh on Balance): Formatted display string (e.g. '29.22 Grams')

      • metrics.solution_normality_n (Solution Normality (N)): Formatted display string (e.g. '0.50 N (eq/L)')

      • metrics.total_moles_dissolved (Total Dissolved Moles): Formatted display string (e.g. '0.500 Moles')

      • metrics.solution_mass_percentage (Approximate Weight/Volume (w/v %)): Formatted display string (e.g. '2.92% (w/v)')

    • execution_time_ms (number): Latency in milliseconds.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "omni_molarity_normality_solution"
  }
}

Input Schema

NameRequiredDescriptionDefault
solute_valence_factorNoValence Factor (Equivalents per Mole) (eq/mol). H⁺ or OH⁻ equivalents (e.g. HCl = 1; H₂SO₄ = 2; H₃PO₄ = 3). Default: 1. Min: 1. Max: 6.
target_molarity_mol_lNoDesired Target Molarity (M in mol/L) (M). Molar concentration of final solution. Default: 0.5. Min: 0.001. Max: 20.
molecular_weight_g_molNoSolute Formula Weight / MW (g/mol) (g/mol). Molecular weight from reagent label (e.g. NaCl = 58.44, NaOH = 40.00). Default: 58.44. Min: 1. Max: 2000.
solution_volume_litersNoTarget Solution Volume (Liters) (L). Total final volume of prepared liquid (1,000 mL = 1.0 L). Default: 1. Min: 0.01. Max: 1000.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.2

TDQS

A4.6/5.0
Behavior5/5

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

With no annotations supplied, the description carries the full burden and does so: it declares the tool read-only, idempotent, stateless, and side-effect free, and explains that out-of-bounds inputs return a diagnostic error status rather than throwing. It also documents the return envelope (status, calculator, category, formula, inputs, metrics, execution_time_ms), which is more than annotations alone would convey.

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

Conciseness4/5

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

The definition is front-loaded with purpose and formula, then cleanly sectioned into usage, behavior, and returns. It is somewhat long and repeats parameter names with units in the WHEN TO USE list, which duplicates the schema, but no section is filler.

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?

Although no output schema exists, the RETURNS section fully enumerates the response fields and their formats, and the behavior section covers validation and error handling. For a four-parameter deterministic calculator, nothing an agent needs to invoke it correctly is missing.

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 schema already documents each parameter's units, defaults, and bounds. The description restates the parameter names with units in the WHEN TO USE block but adds no new syntax, format, or edge-case meaning beyond what the schema provides, so the baseline of 3 applies.

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?

The description names a specific verb and resource ('Calculate chemical solute mass required in grams to prepare precise laboratory solutions') and states the governing formulas for molarity and normality. It also distinguishes itself from the generic dispatcher omni_universal_query, so an agent can identify its role without opening the schema.

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

Usage Guidelines5/5

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

Explicit WHEN TO USE lists the exact computed outputs and the inputs that drive them, WHEN NOT TO USE excludes qualitative/unquantified reasoning, and SIBLING ROUTING names omni_universal_query as the alternative for cross-discipline dispatch. The conditions that select this tool versus the alternative are stated directly.

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