STEM Calc MCP

Solution math

solution_math

Read-only

Calculate molarity or dilution values by entering known moles, liters, volumes, and concentrations; omit the unknown value and solve with M = mol/L or M1V1 = M2V2.

Instructions

Solve molarity (M = mol/L) or a dilution (M1V1 = M2V2). Leave out the one value you want and it is solved. Volumes are in liters.

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": {
      "mode": "<mode>"
    },
    "name": "solution_math"
  }
}

Input Schema

Name	Required	Description
`mode`	Yes	molarity solves M = mol/L. dilution solves M1V1 = M2V2.
`moles`	No	Moles of solute. Molarity mode only.
`liters`	No	Volume of the solution in liters. Molarity mode only.
`molarity`	No	Concentration in mol/L. Molarity mode only.
`finalLiters`	No	Final volume V2 in liters. Dilution mode only.
`finalMolarity`	No	Final concentration M2 in mol/L. Dilution mode only.
`initialLiters`	No	Starting volume V1 in liters. Dilution mode only.
`initialMolarity`	No	Starting concentration M1 in mol/L. Dilution mode only.

Output Schema

Name	Required	Description	Default
`result`	Yes
`solved`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Addedv0.1.3Nov 2, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds real behavioral context: unit convention (liters) and the omit-one-unknown solving model. It doesn't say what happens on over-specification or contradictory inputs, which is the only remaining gap.

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?

Three short sentences, front-loaded with the formulas, then the calling convention, then the unit constraint. No filler and nothing repeated from the schema verbatim beyond a one-clause unit reminder.

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?

With an output schema present, return values needn't be explained, and mode selection plus the omission rule cover the 8-parameter surface well. Minor omission: no statement of error behavior when too many or too few values are given for a mode.

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, and the description earns above that by explaining the omission semantics that the schema never states — that you supply all but one value and which quantity is solved for. The liter convention is redundant with the schema's per-parameter text but reinforces the mode-specific grouping.

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 and resource ("Solve molarity ... or a dilution") and names the governing equations (M = mol/L, M1V1 = M2V2), which immediately separates it from siblings like molar_mass or stoichiometry. An agent knows exactly what computation this tool performs.

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?

"Leave out the one value you want and it is solved" gives the agent a concrete calling convention that isn't in the schema (only `mode` is required). It doesn't name when to prefer a sibling for related calculations, but for a self-contained calculator the guidance needed to invoke it correctly is present.

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

Deploy Server