Atlarium Habitat Database MCP

Search fish

search_fish

Read-onlyIdempotent

Search fish and aquatic animal profiles in the Atlarium habitat database.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search_fish"
  }
}

Input Schema

Name	Required	Description
`limit`	No	Maximum number of public records to return, up to 50.
`query`	No	Search text used to match public Atlarium records.
`gh_max`	No	Maximum general hardness filter.
`gh_min`	No	Minimum general hardness filter.
`kh_max`	No	Maximum carbonate hardness filter.
`kh_min`	No	Minimum carbonate hardness filter.
`offset`	No	Zero-based pagination offset for public search results.
`ph_max`	No	Maximum acceptable pH filter.
`ph_min`	No	Minimum acceptable pH filter.
`language`	No	Optional preferred response language: it, en or es.
`care_level`	No	Care-level filter, for example easy, moderate or expert.
`temperament`	No	Temperament filter, for example peaceful or aggressive.
`max_tank_liters`	No	Maximum tank volume filter in liters.
`min_tank_liters`	No	Minimum tank volume filter in liters.
`temperature_max`	No	Maximum temperature filter in Celsius.
`temperature_min`	No	Minimum temperature filter in Celsius.

Output Schema

Name	Required	Description	Default
`data`	Yes
`tool`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

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

Changed16 schema fields changedJun 20, 2026

addedInput schema / properties / care_level / description

Added value: +"Care-level filter, for example easy, moderate or expert."

addedInput schema / properties / gh_max / description
```
Added value: +"Maximum general hardness filter."
```
addedInput schema / properties / gh_min / description
```
Added value: +"Minimum general hardness filter."
```

addedInput schema / properties / kh_max / description

Added value: +"Maximum carbonate hardness filter."

addedInput schema / properties / kh_min / description

Added value: +"Minimum carbonate hardness filter."

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 public records to return, up to 50."

addedInput schema / properties / max_tank_liters / description
```
Added value: +"Maximum tank volume filter in liters."
```
addedInput schema / properties / min_tank_liters / description
```
Added value: +"Minimum tank volume filter in liters."
```

addedInput schema / properties / offset / description

Added value: +"Zero-based pagination offset for public search results."

addedInput schema / properties / ph_max / description
```
Added value: +"Maximum acceptable pH filter."
```
addedInput schema / properties / ph_min / description
```
Added value: +"Minimum acceptable pH filter."
```

addedInput schema / properties / query / description

Added value: +"Search text used to match public Atlarium records."

addedInput schema / properties / temperament / description

Added value: +"Temperament filter, for example peaceful or aggressive."

addedInput schema / properties / temperature_max / description
```
Added value: +"Maximum temperature filter in Celsius."
```
addedInput schema / properties / temperature_min / description
```
Added value: +"Minimum temperature filter in 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

B3.3/5.0

Behavior2/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is clear. However, the description adds no additional behavioral context such as return format, pagination defaults, or filtering scope beyond what the schema states. Nothing contradicts the annotations, but no extra value is provided.

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, focused sentence with no redundant wording. It front-loads the action and resource, earning every word it uses.

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?

For a search tool with 16 parameters but a rich schema and output schema, the one-line description is minimally viable. It states the core purpose but lacks usage context or behavioral details, which would help an agent select it among many sibling search tools. Structured data covers a lot, but the description alone leaves gaps in when/how to use it.

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 for all 16 parameters, each with clear descriptions. The tool description itself adds no parameter-level information, so the baseline of 3 is appropriate given that the schema fully documents the parameters.

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 uses a specific verb ('Search') and clearly identifies the resource ('fish and aquatic animal profiles') within a defined context ('Atlarium habitat database'). This distinguishes it from sibling search tools like search_plants or search_diseases.

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?

The description provides no guidance on when to use this tool versus alternatives, nor does it mention any exclusions or prerequisites. Siblings like get_fish_profile or search_plants exist, but no comparison or selection criteria are given.

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

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.