Atlarium Habitat Database MCP

Calculate tank volume

calculate_tank_volume

Read-onlyIdempotent

Calculate gross and net aquarium volume estimates from dimensions.

Input Schema

TableJSON Schema

Name	Required	Description
`shape`	Yes	Tank shape: rectangular, cylindrical or bow-front.
`width_cm`	No	Tank width in centimeters.
`height_cm`	No	Tank height in centimeters.
`length_cm`	No	Tank length in centimeters.
`diameter_cm`	No	Cylinder diameter in centimeters.
`bow_depth_cm`	No	Curved front depth in centimeters for bow-front tanks.
`water_height_cm`	No	Actual filled water height in centimeters.
`glass_thickness_mm`	No	Glass thickness in millimeters for net volume estimates.
`substrate_depth_cm`	No	Substrate depth in centimeters.
`water_density_kg_per_liter`	No	Water density in kilograms per liter.
`hardscape_displacement_liters`	No	Estimated hardscape displacement in liters.

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"
+]

Changed11 schema fields changedJun 20, 2026
- addedInput schema / properties / bow_depth_cm / description
```
Added value: +"Curved front depth in centimeters for bow-front tanks."
```
- addedInput schema / properties / diameter_cm / description
```
Added value: +"Cylinder diameter in centimeters."
```
- addedInput schema / properties / glass_thickness_mm / description
```
Added value: +"Glass thickness in millimeters for net volume estimates."
```
- addedInput schema / properties / hardscape_displacement_liters / description
```
Added value: +"Estimated hardscape displacement in liters."
```
- addedInput schema / properties / height_cm / description
```
Added value: +"Tank height in centimeters."
```
- addedInput schema / properties / length_cm / description
```
Added value: +"Tank length in centimeters."
```
- addedInput schema / properties / shape / description
```
Added value: +"Tank shape: rectangular, cylindrical or bow-front."
```
- addedInput schema / properties / substrate_depth_cm / description
```
Added value: +"Substrate depth in centimeters."
```
- addedInput schema / properties / water_density_kg_per_liter / description
```
Added value: +"Water density in kilograms per liter."
```
- addedInput schema / properties / water_height_cm / description
```
Added value: +"Actual filled water height in centimeters."
```
- addedInput schema / properties / width_cm / description
```
Added value: +"Tank width in centimeters."
```
AddedJun 20, 2026

TDQS

A3.7/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, covering the safety profile. The description adds the behavioral distinction between 'gross' and 'net' estimates and the word 'estimates' signaling approximate results. No contradictions with annotations.

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 a single, concise sentence that is front-loaded with the action and resource. Every word earns its place, with no unnecessary detail or repetition.

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 has 11 parameters and shape-specific logic (rect, cyl, bow), but the description lacks guidance on how to select dimensions per shape. However, the schema's parameter descriptions and the existing output schema compensate partially, making the description minimally adequate.

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?

All 11 parameters have descriptions in the input schema (100% coverage), so the baseline is 3. The description only mentions 'dimensions' generically and does not add any parameter-specific meaning beyond what the schema already provides.

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 states the tool's purpose with a specific verb ('Calculate'), resource ('aquarium volume'), and scope ('gross and net... from dimensions'). It distinguishes itself from sibling calculators like calculate_tank_weight and calculate_water_change by focusing on volume estimates.

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 phrase 'from dimensions' implies the tool is used when dimensions are available, but it provides no explicit guidance on when to use this tool over alternatives such as calculate_tank_weight. No exclusions or alternative tool references are given, so usage context is only implied.

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.