Skip to main content
Glama

Atlarium Habitat Database MCP

by bio.atlarium
OverviewAdmin

Get product profile

get_product_profile
Read-onlyIdempotent

Get a structured public habitat product profile using the exact slug returned by search_products.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
slugYesExact safe slug path 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: -"Safe public Atlarium slug path made of one or more path segments."New value: +"Exact safe slug path 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: +"Safe public Atlarium slug path made of one or more path segments."
  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.3/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 fully covered. The description adds context about the result being 'structured' and 'public', but does not disclose additional behavioral traits (e.g., rate limits, authentication needs) beyond what annotations provide. With strong annotations, this is acceptable.

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, front-loaded sentence with no unnecessary words. Every piece of information earns its place: verb, resource, modifier ('structured public'), and the precondition linking to search_products.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool has only two parameters (one required), an output schema (not shown), and comprehensive annotations. The description covers the key behavioral context (precondition, public nature) and parameter semantics for the critical slug field. For a simple lookup tool, this is fully sufficient.

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 for the slug parameter by specifying it must come from 'search_products', which is more explicit than the schema's 'related Atlarium search tool'. The language parameter is not mentioned in the description, but the schema already documents its enum values and optionality. Overall, the description enhances understanding of the most critical parameter.

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 ('Get') and resource ('structured public habitat product profile'), and distinguishes this tool from siblings like get_fish_profile or get_plant_profile by specifying the resource type and the precondition ('using the exact slug returned by search_products').

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 states when to use this tool: after retrieving a slug from search_products. This provides clear context and a prerequisite but does not explicitly state when not to use it or list alternative tools. However, the resource name and precondition make the intended usage unambiguous.

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