Atlarium Habitat Database MCP

Convert units

convert_units

Read-onlyIdempotent

Convert aquarium-relevant temperature, length, weight and volume units.

Input Schema

TableJSON Schema

Name	Required	Description
`length`	No	Length conversion input.
`volume`	No	Volume conversion input.
`weight`	No	Weight conversion input.
`temperature`	No	Temperature conversion input.
`temperature_delta`	No	Temperature difference 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"
+]

Changed15 schema fields changedJun 20, 2026
- addedInput schema / properties / length / description
```
Added value: +"Length conversion input."
```
- addedInput schema / properties / length / properties / unit / description
```
Added value: +"Length input unit."
```
- addedInput schema / properties / length / properties / value / description
```
Added value: +"Length value to convert."
```
- addedInput schema / properties / temperature / description
```
Added value: +"Temperature conversion input."
```
- addedInput schema / properties / temperature / properties / unit / description
```
Added value: +"Temperature input unit."
```
- addedInput schema / properties / temperature / properties / value / description
```
Added value: +"Temperature value to convert."
```
- addedInput schema / properties / temperature_delta / description
```
Added value: +"Temperature difference input."
```
- addedInput schema / properties / temperature_delta / properties / from_c / description
```
Added value: +"Starting temperature in Celsius."
```
- addedInput schema / properties / temperature_delta / properties / to_c / description
```
Added value: +"Target temperature in Celsius."
```
- addedInput schema / properties / volume / description
```
Added value: +"Volume conversion input."
```
- addedInput schema / properties / volume / properties / unit / description
```
Added value: +"Volume input unit."
```
- addedInput schema / properties / volume / properties / value / description
```
Added value: +"Volume value to convert."
```
- addedInput schema / properties / weight / description
```
Added value: +"Weight conversion input."
```
- addedInput schema / properties / weight / properties / unit / description
```
Added value: +"Weight input unit."
```
- addedInput schema / properties / weight / properties / value / description
```
Added value: +"Weight value to convert."
```
AddedJun 20, 2026

TDQS

A3.5/5.0

Behavior3/5

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

Annotations already indicate read-only, idempotent, non-destructive behavior. The description adds the aquarium-relevant scope but omits mention of temperature_delta support and the ability to handle multiple conversion types in a single call. No contradiction 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 9-word sentence that immediately states the verb and scope. No redundant information or filler.

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 description omits the temperature_delta input category, which is a fifth parameter in the schema. While the schema and output schema are rich, the description fails to fully enumerate the tool's capabilities, creating a mismatch between the stated categories and actual parameters. This prevents a higher score.

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?

The input schema has 100% description coverage with detailed enums and constraints for each unit category. The tool description merely lists categories (temperature, length, weight, volume) without adding parameter-specific semantics beyond what the schema provides. Baseline 3 is appropriate as schema carries the weight.

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 converts aquarium-relevant units across four categories (temperature, length, weight, volume), using a specific verb and resource. It distinguishes itself from sibling calculation tools, which focus on specific aquarium computations rather than generic unit conversion.

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?

No guidance is provided on when to use this tool versus alternatives. The description does not mention exclusions, use cases, or relationships to sibling calculation tools. The agent must infer that conversion is a prerequisite or separate operation.

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.