Skip to main content
Glama

Molarity Calculator

calculator_molarity
Read-only

Solve M = n / V. Volume in L (mL accepted).

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": "calculator_molarity"
  }
}

Input Schema

NameRequiredDescriptionDefault
molesNoMoles of solute.
volumeNoVolume in L or mL.
molarityNoMolarity in mol/L.

Output Schema

NameRequiredDescriptionDefault
molesNo
molarityNo
volume_LNo
expressionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already specify read-only, non-destructive, closed-world behavior, so the description only needs to add useful context. It adds the formula and unit handling, but it does not clarify whether the tool computes molarity only or can solve for any missing variable among moles, volume, and molarity.

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 two short sentences with no wasted words, and the core operation is front-loaded as a formula. Its brevity is appropriate for a simple calculator, even though it could be more complete.

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

Completeness3/5

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

The tool is simple and benefits from a fully described schema, annotations, and an output schema. However, because all three parameters are optional, the description should clarify whether two inputs are supplied to solve for the third; the current formula-only wording leaves that invocation pattern ambiguous.

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 all three parameters. The description mentions volume units, which matches the schema, and the formula gives some relational meaning, but it adds no parameter guidance beyond what the schema provides.

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 formula, M = n / V, which makes the operation clear: calculating molarity from moles and volume. It does not differentiate the tool from nearby siblings such as calculator_concentration, calculator_moles, or calculator_dilution, so it falls short of a 5.

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

Usage Guidelines2/5

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

The description gives the formula and volume units but no guidance on when to use this tool instead of related calculators. It does not mention alternatives, exclusions, or prerequisite conditions.

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.