Scientific Calculator

Moles Calculator

calculator_moles

Read-only

Solve n = m / M for moles, mass (g), or molar mass (g/mol). Formula can supply M.

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_moles"
  }
}

Input Schema

Name	Required	Description
`mass`	No	Mass in grams.
`moles`	No	Amount in mol.
`formula`	No	Optional formula to compute molar mass.
`molar_mass`	No	Molar mass in g/mol.

Output Schema

Name	Required	Description	Default
`moles`	No
`mass_g`	No
`expression`	Yes
`molar_mass`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

B3.3/5.0

Behavior3/5

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

The annotations already declare this to be a read-only, non-destructive, closed-world calculation. The description adds the core computational behavior—solving the same equation for any one of three variables—but does not explain what happens with invalid formulas, ambiguous inputs, or which two values must be supplied.

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 short sentences with no filler. The equation and the main input options are front-loaded, and nothing is wasted.

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?

An output schema exists, so return values need not be explained. However, with zero required parameters and four optional ones, the description should clarify that the agent must supply enough values to solve the equation and how formula and molar_mass interact if both are provided.

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 coverage is 100%, so the schema already documents each parameter and its units. The description adds the equation being solved and reinforces that formula can provide molar mass, but it does not clarify the important combination rule when no parameters are required.

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?

States a specific operation: solving n = m / M for moles, mass, or molar mass, with units. That is clear enough to identify the resource and operation, but it does not distinguish this tool from nearby siblings such as calculator_molar_mass or calculator_stoichiometry.

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?

There is no guidance on when to use this tool rather than calculator_molar_mass, calculator_stoichiometry, or calculator_concentration. The note that 'Formula can supply M' hints at one input path, but no usage context or exclusions are given.

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

All Scientific Calculator 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.