Skip to main content
Glama
Sign In

Atlarium Habitat Database MCP

by bio.atlarium
OverviewDiscussionsAdmin

Get fish profile

get_fish_profile
Read-onlyIdempotent

Get a structured fish or aquatic animal profile using the exact slug returned by search_fish.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "slug": "<slug>"
    },
    "name": "get_fish_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesExact single-segment slug returned by the related Atlarium search tool.
languageNoOptional preferred response language: it, en or es.

Output Schema

NameRequiredDescriptionDefault
dataYes
toolYes

Schema Changelog

Changes observed during successful MCP inspections.

  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/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, covering the safety profile. The description adds that the returned data is a 'structured profile' and that the slug must be exact from search_fish, which is useful but not substantial beyond the annotations. No contradiction present.

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?

A single, front-loaded sentence that immediately states the action and resource, then adds the critical usage context. Every word earns its place—no fluff or repetition.

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 presence of an output schema (context signal: true), the description does not need to detail return values. It adequately covers input source, scope, and the fact that the result is a structured profile. It could optionally mention the language parameter, but that is optional and described in the schema. Complete for its purpose.

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 description coverage is 100%, so the schema already documents both parameters well. The description merely reinforces that the slug must come from search_fish, which is already stated in the schema for the slug parameter. It adds no new meaning to the language parameter. Baseline 3 is appropriate.

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 action ('Get a structured... profile') and the specific resource ('fish or aquatic animal'). It explicitly references the required input source ('exact slug returned by search_fish'), which strongly distinguishes it from sibling profile-retrieval tools like get_algae_profile or get_plant_profile.

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 provides clear context by stating the prerequisite (use search_fish first to obtain the slug) and implies the tool is for fetching full details after search. It does not explicitly state when not to use it or name alternatives, but the sibling set makes the intended workflow obvious. Slightly below perfect for lacking explicit exclusions.

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

Resources