Atlarium Habitat Database MCP

Calculate water chemistry

calculate_water_chemistry

Read-onlyIdempotent

Calculate public water chemistry conversions, CO2, salinity and water-mix estimates.

Input Schema

TableJSON Schema

Name	Required	Description
`co2`	No	CO2 estimation input from KH and pH.
`salinity`	No	Salinity calculation input.
`water_mix`	No	Water-mixing calculation input.
`general_hardness`	No	General hardness conversion input.
`carbonate_hardness`	No	Carbonate hardness conversion input.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`data`	Yes
`tool`	Yes

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

Changed2 schema fields changedJul 2, 2026

removedOutput schema / properties / generated_at
```
Removed value: -{
-  "type": "string"
-}
```

changedOutput schema / required

Previous value: -[
-  "data",
-  "generated_at",
-  "tool"
-]New value: +[
+  "data",
+  "tool"
+]

Changed20 schema fields changedJun 20, 2026
- addedInput schema / properties / carbonate_hardness / description
```
Added value: +"Carbonate hardness conversion input."
```
- addedInput schema / properties / carbonate_hardness / properties / unit / description
```
Added value: +"Carbonate hardness input unit."
```
- addedInput schema / properties / carbonate_hardness / properties / value / description
```
Added value: +"Carbonate hardness value."
```
- addedInput schema / properties / co2 / description
```
Added value: +"CO2 estimation input from KH and pH."
```
- addedInput schema / properties / co2 / properties / kh_dkh / description
```
Added value: +"Carbonate hardness in dKH."
```
- addedInput schema / properties / co2 / properties / ph / description
```
Added value: +"Water pH value on the 0 to 14 scale."
```
- addedInput schema / properties / general_hardness / description
```
Added value: +"General hardness conversion input."
```
- addedInput schema / properties / general_hardness / properties / unit / description
```
Added value: +"General hardness input unit."
```
- addedInput schema / properties / general_hardness / properties / value / description
```
Added value: +"General hardness value."
```
- addedInput schema / properties / salinity / description
```
Added value: +"Salinity calculation input."
```
- addedInput schema / properties / salinity / properties / current_ppt / description
```
Added value: +"Current salinity in parts per thousand."
```
- addedInput schema / properties / salinity / properties / salinity_ppt / description
```
Added value: +"Measured or source salinity in parts per thousand."
```
- addedInput schema / properties / salinity / properties / target_ppt / description
```
Added value: +"Target salinity in parts per thousand."
```
- addedInput schema / properties / salinity / properties / temperature_c / description
```
Added value: +"Water temperature in Celsius for salinity adjustment."
```
- addedInput schema / properties / salinity / properties / volume_liters / description
```
Added value: +"Water volume in liters for salinity calculations."
```
- addedInput schema / properties / water_mix / description
```
Added value: +"Water-mixing calculation input."
```
- addedInput schema / properties / water_mix / properties / source1_gh / description
```
Added value: +"General hardness of source water 1."
```
- addedInput schema / properties / water_mix / properties / source2_gh / description
```
Added value: +"General hardness of source water 2."
```
- addedInput schema / properties / water_mix / properties / target_gh / description
```
Added value: +"Target general hardness for the mix."
```
- addedInput schema / properties / water_mix / properties / total_liters / description
```
Added value: +"Total mixed water volume in liters."
```
AddedJun 20, 2026

TDQS

A3.8/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds only that outputs are 'estimates,' which is mild behavioral context; it does not describe result shape or edge cases.

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?

A single, grammatically simple sentence with all key terms front-loaded; no redundant or filler content.

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, rich annotations, and full parameter descriptions, the one-sentence description suffices to convey the tool's scope. It could be slightly more explicit that the caller should provide one of the sub-objects, but the schema already reveals that 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%, so the input schema fully documents all parameters and nested objects. The description adds no parameter-level details beyond naming the calculation areas, so baseline 3 is appropriate.

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 clearly identifies the tool as calculating water chemistry conversions, CO2, salinity, and water-mix estimates, using a specific verb and resource list. This distinguishes it from sibling calculators like calculate_tank_volume or convert_units.

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

Usage Guidelines3/5

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

The listed capabilities imply when the tool is relevant, but the description provides no explicit guidance on when to use this calculator versus sibling calculate_* tools, nor does it caution about selecting one of the multiple input modes. It is minimally viable but not proactive.

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

All Atlarium Habitat Database MCP tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.