Scientific Calculator

Concentration Calculator

calculator_concentration

Read-only

Mass concentration (g/L), molarity, mass %, or volume %.

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": {
      "type": "<type>"
    },
    "name": "calculator_concentration"
  }
}

Input Schema

Name	Required	Description
`mass`	No	Mass in g (mass concentration or solute).
`type`	Yes	mass_concentration\|molar\|mass_percent\|volume_percent
`moles`	No	Moles for molar concentration.
`volume`	No	Volume L/mL.
`solute_mass`	No	Solute mass for mass %.
`solute_volume`	No	Solute volume for volume %.
`solution_mass`	No	Solution mass for mass %.
`solution_volume`	No	Solution volume for volume %.

Output Schema

Name	Required	Description	Default
`type`	No
`unit`	No
`value`	Yes
`expression`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

C2.8/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds the supported concentration modes but does not disclose mode-dependent input behavior, assumptions, or output details, and it does not contradict the annotations.

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

Conciseness3/5

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

The description is a single front-loaded fragment with no wasted words, but it is under-specified for an eight-parameter, four-mode calculator rather than appropriately structured. The brevity does not earn full credit because necessary routing and mode detail are absent.

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 described, and the schema documents each parameter. However, the description omits the critical mapping between each type and the parameters needed (e.g., solute_mass + solution_mass for mass_percent, moles + volume for molar), leaving the agent to infer key call structure.

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% and all eight parameters are documented in the schema. The description only repeats the four type modes and adds no extra meaning such as which parameters are required for each mode.

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

Purpose3/5

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

The description supplies only a noun list of concentration types ('Mass concentration (g/L), molarity, mass %, or volume %') without an explicit verb or scope statement; combined with the title it is inferable but not clearly stated. It also does not distinguish this tool from close siblings such as calculator_molarity, calculator_dilution, or calculator_moles.

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 when-to-use, when-not-to-use, or alternatives guidance. The description merely lists supported concentration modes, leaving the agent to infer that this is the multi-mode concentration calculator versus single-purpose siblings.

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.