Atlarium Habitat Database MCP

Calculate equipment requirements

calculate_equipment_requirements

Read-onlyIdempotent

Calculate advisory heater, lighting and electricity requirements.

Input Schema

TableJSON Schema

Name	Required	Description
`heater`	No	Heater sizing input.
`lighting`	No	Lighting estimate input.
`electricity`	No	Electricity cost and usage calculation 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"
+]

Changed14 schema fields changedJun 20, 2026
- addedInput schema / properties / electricity / description
```
Added value: +"Electricity cost and usage calculation input."
```
- addedInput schema / properties / electricity / properties / cost_per_kwh / description
```
Added value: +"Electricity cost per kWh."
```
- addedInput schema / properties / electricity / properties / duty_cycle_percent / description
```
Added value: +"Estimated duty cycle percentage."
```
- addedInput schema / properties / electricity / properties / hours_per_day / description
```
Added value: +"Daily runtime in hours."
```
- addedInput schema / properties / electricity / properties / wattage / description
```
Added value: +"Equipment wattage."
```
- addedInput schema / properties / heater / description
```
Added value: +"Heater sizing input."
```
- addedInput schema / properties / heater / properties / ambient_c / description
```
Added value: +"Ambient room temperature in Celsius."
```
- addedInput schema / properties / heater / properties / insulation / description
```
Added value: +"Tank insulation quality."
```
- addedInput schema / properties / heater / properties / target_c / description
```
Added value: +"Target water temperature in Celsius."
```
- addedInput schema / properties / heater / properties / volume_liters / description
```
Added value: +"Tank volume in liters for heater sizing."
```
- addedInput schema / properties / lighting / description
```
Added value: +"Lighting estimate input."
```
- addedInput schema / properties / lighting / properties / lumens / description
```
Added value: +"Lighting output in lumens."
```
- addedInput schema / properties / lighting / properties / volume_liters / description
```
Added value: +"Tank volume in liters for lighting estimates."
```
- addedInput schema / properties / lighting / properties / watts / description
```
Added value: +"Lighting wattage."
```
AddedJun 20, 2026

TDQS

B3.1/5.0

Behavior2/5

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

Annotations already declare the tool as read-only, idempotent, and non-destructive. The description adds only the word 'advisory,' which hints at recommend output, but provides no further behavioral context such as assumptions, formulas, or edge-case handling. This is minimal additional transparency beyond what annotations already cover.

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, front-loaded sentence with no wasted words. It efficiently communicates the tool's scope without unnecessary detail.

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 three nested input objects and an output schema, so some complexity is present. The description is minimal but adequate, covering the main categories. However, it could be improved by stating the advisory nature and explaining what the outputs represent, though the schema compensates for most gaps.

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 complete (100%) description coverage for all nested objects and properties, so the baseline is 3. The description simply names the three categories (heater, lighting, electricity) and does not add parameter-level meaning beyond the schema.

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?

The description clearly states the tool calculates heater, lighting, and electricity requirements, using the verb 'calculate' and naming specific resources. It distinguishes from sibling calculators by naming these three equipment types, though it could be more explicit about the advisory/recommendation nature.

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 explicit guidance on when to use this tool versus alternatives. The description implies usage for equipment calculations but does not mention exclusions, prerequisites, or alternative tools, leaving the decision to the agent.

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.