Skip to main content
Glama

Atlarium Habitat Database MCP

by bio.atlarium
OverviewAdmin

Get plant profile

get_plant_profile
Read-onlyIdempotent

Get a structured aquatic plant profile using the exact slug returned by search_plants.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
slugYesExact single-segment slug returned by the related Atlarium search tool.
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. Changed2 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."
  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.2/5.0
Behavior4/5

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

The annotations already indicate read-only, idempotent, and non-destructive behavior. The description confirms a safe lookup operation without contradictions, adding clarity about the slug dependency.

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 sentence that efficiently conveys the core purpose and prerequisite. No extraneous information, perfectly front-loaded.

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?

Given the existence of an output schema and complete parameter descriptions, the description adequately covers the missing context (slug source). Slightly more could be said about language behavior, but not necessary.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3. The description adds value by referencing the provenance of the slug (from search_plants), and the schema already provides detailed constraints and descriptions for both 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 clearly states it retrieves a structured aquatic plant profile using a specific identifier. It distinguishes itself from sibling tools like search_plants by explicitly requiring the slug from that tool.

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

Usage Guidelines3/5

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

The description provides clear guidance to use the slug from search_plants, but does not mention when to use alternatives or when not to use this tool. It implies usage after a search but lacks exclusion criteria.

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