Atlarium Habitat Database MCP

Suggest species for tank

suggest_species_for_tank

Read-onlyIdempotent

Suggest compatible aquatic species based on tank size and water parameters.

Input Schema

TableJSON Schema

Name	Required	Description
`gh`	No	Water hardness, conductivity or TDS-style value for advisory matching.
`kh`	No	Water hardness, conductivity or TDS-style value for advisory matching.
`ph`	No	Water pH value on the 0 to 14 scale.
`limit`	No	Maximum number of suggestions to return, up to 30.
`language`	No	Optional preferred response language: it, en or es.
`tank_liters`	Yes	Tank or habitat volume in liters.
`temperature`	No	Water or ambient temperature in degrees Celsius.
`planted_tank`	No	When true, prefer suggestions compatible with planted aquariums.
`beginner_friendly`	No	When true, prefer species that are suitable for beginners.

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

Changed9 schema fields changedJun 20, 2026

addedInput schema / properties / beginner_friendly / description

Added value: +"When true, prefer species that are suitable for beginners."

addedInput schema / properties / gh / description

Added value: +"Water hardness, conductivity or TDS-style value for advisory matching."

addedInput schema / properties / kh / description

Added value: +"Water hardness, conductivity or TDS-style value for advisory matching."

addedInput schema / properties / language / description

Added value: +"Optional preferred response language: it, en or es."

addedInput schema / properties / limit / description

Added value: +"Maximum number of suggestions to return, up to 30."

addedInput schema / properties / ph / description

Added value: +"Water pH value on the 0 to 14 scale."

addedInput schema / properties / planted_tank / description

Added value: +"When true, prefer suggestions compatible with planted aquariums."

addedInput schema / properties / tank_liters / description
```
Added value: +"Tank or habitat volume in liters."
```

addedInput schema / properties / temperature / description

Added value: +"Water or ambient temperature in degrees Celsius."

Changed1 schema field changedJun 19, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "data": {},
+    "generated_at": {
+      "type": "string"
+    },
+    "tool": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "data",
+    "generated_at",
+    "tool"
+  ],
+  "type": "object"
+}

First observedJun 17, 2026

TDQS

A3.5/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 known. The description adds context by specifying that suggestions are 'based on tank size and water parameters,' which communicates scope. However, it does not reveal additional behavior such as ranking, default behavior when parameters are missing, or output size.

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 one 12-word sentence, extremely efficient, and front-loaded with the verb and object. Every word contributes to stating the core purpose with zero waste. This meets the standard of appropriately concise.

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?

With good annotations, a fully described schema, and an output schema present, the description only needs to add context for when to use the tool. It explains the core inputs but does not distinguish from closely related siblings like 'suggest_habitat_for_tank' or 'check_species_compatibility', leaving the context only partially complete.

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 every parameter is already documented with descriptions. The description's mention of 'tank size and water parameters' aligns with the schema but adds no new details beyond it. Baseline of 3 is appropriate because the schema carries the burden.

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 function: 'Suggest compatible aquatic species based on tank size and water parameters.' It uses a specific verb ('suggest') and resource ('species') and differentiates from sibling tools like 'suggest_habitat_for_tank' (habitats) and 'check_species_compatibility' (checking existing species).

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. Unlike the high-calibration example that names a sibling tool for alternative scenarios, this description does not mention 'check_species_compatibility' or 'suggest_habitat_for_tank' as alternatives, nor any conditions for use.

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.