Atlarium Habitat Database MCP

Search plants

search_plants

Read-onlyIdempotent

Search aquatic plants in the Atlarium database.

Input Schema

TableJSON 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.
`offset`	No	Zero-based pagination offset for public search results.
`language`	No	Optional preferred response language: it, en or es.
`placement`	No	Aquascape placement filter such as foreground or background.
`difficulty`	No	Plant difficulty filter.
`growth_rate`	No	Growth-rate filter.
`co2_requirement`	No	CO2 requirement filter.
`light_requirement`	No	Lighting requirement filter.

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 / co2_requirement / description
```
Added value: +"CO2 requirement filter."
```
- addedInput schema / properties / difficulty / description
```
Added value: +"Plant difficulty filter."
```
- addedInput schema / properties / growth_rate / description
```
Added value: +"Growth-rate filter."
```
- addedInput schema / properties / language / description
```
Added value: +"Optional preferred response language: it, en or es."
```
- addedInput schema / properties / light_requirement / description
```
Added value: +"Lighting requirement filter."
```
- addedInput schema / properties / limit / description
```
Added value: +"Maximum number of public records to return, up to 50."
```
- addedInput schema / properties / offset / description
```
Added value: +"Zero-based pagination offset for public search results."
```
- addedInput schema / properties / placement / description
```
Added value: +"Aquascape placement filter such as foreground or background."
```
- addedInput schema / properties / query / description
```
Added value: +"Search text used to match public Atlarium records."
```

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, idempotentHint=true, and destructiveHint=false, so the safety profile is clear. However, the description adds no behavioral context beyond the verb 'search'—it does not disclose pagination, filtering semantics, or any limitations. It is consistent with annotations but contributes no extra transparency.

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, tightly worded sentence with no padding or redundancy. It front-loads the essential action and object, making it instantly scannable.

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?

Given the tool's complexity (9 optional parameters, output schema exists), the description is minimally adequate. The schema and output schema fill in the gaps for parameter semantics and return structure. However, the description does not convey the overall search scope (e.g., what fields are matched), which could help an agent decide if this tool fits the task. It is not incomplete enough to be unusable.

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% coverage—every parameter has a descriptive comment. The tool description itself does not add meaning to the parameters; it only names the resource. This matches the baseline of 3 when schema coverage is high.

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: 'Search aquatic plants in the Atlarium database.' It specifies an action (search), a resource (aquatic plants), and a context (Atlarium database). This distinguishes it from sibling search tools like search_fish or search_algae, which target different domains.

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. It does not mention exclusions, prerequisites, or preferred scenarios. The sibling list implies a family of search tools, but the description does not explicitly differentiate when search_plants is the right choice.

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.