Skip to main content
Glama

Atlarium Habitat Database MCP

by bio.atlarium
OverviewAdmin

Get water parameters

get_water_parameters
Read-onlyIdempotent

Get recommended water parameters using the exact slug returned by search_fish or search_plants.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
slugYesExact single-segment slug returned by the related Atlarium search tool.
typeYesProfile type to read water parameters for.
languageNoOptional preferred response language: it, en or es.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataYes
toolYes

Schema Changelog

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

  1. Changed1 schema field changed
    • changedInput schema / properties / slug / description
      Previous value: -"Single safe public Atlarium slug without path separators."New value: +"Exact single-segment slug returned by the related Atlarium search tool."
  2. Changed2 schema fields changed
    • removedOutput schema / properties / generated_at
      Removed value: -{
-  "type": "string"
-}
    • changedOutput schema / required
      Previous value: -[
-  "data",
-  "generated_at",
-  "tool"
-]New value: +[
+  "data",
+  "tool"
+]
  3. Changed3 schema fields changed
    • addedInput schema / properties / language / description
      Added value: +"Optional preferred response language: it, en or es."
    • addedInput schema / properties / slug / description
      Added value: +"Single safe public Atlarium slug without path separators."
    • addedInput schema / properties / type / description
      Added value: +"Profile type to read water parameters for."
  4. Changed1 schema field changed
    • 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"
+}
  5. First observed

TDQS

A4/5.0
Behavior3/5

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

Annotations already indicate readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is clear. The description does not add additional behavioral context beyond the slug dependency, such as whether it reads live data or cached results, or any rate limit considerations. It appropriately avoids contradicting 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, clear sentence that conveys the tool's exact purpose and dependency. It contains no filler words and is front-loaded with the main action and resource.

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?

The tool has a well-described input schema, annotations, and sibling context. The description is complete for its role as a simple lookup tool, explicitly linking to search functions. It could optionally mention the output is a human-readable parameter set, but the presence of an output schema reduces the need for such detail.

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 coverage is 100%, so the input schema already describes all three parameters with types, enums, and constraints. The description adds no further parameter semantics beyond reiterating the slug's source, but the schema baseline is sufficient, resulting in a score of 3.

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 retrieves recommended water parameters using an exact slug from search_fish or search_plants. It specifies the verb ('get'), the resource ('water parameters'), and the direct dependency on sibling search tools, distinguishing it from other get_* and calculate_* tools.

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

Usage Guidelines4/5

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

The description explicitly instructs to use the slug returned by search_fish or search_plants, which implies the correct usage order (search first, then this tool). It does not explicitly state when not to use it or list alternatives, but the context of sibling tools makes its purpose clear.

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 toolsInspect
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.

Resources