Catalogueoflife

Classification

classification

Read-onlyIdempotent

"What kingdom / phylum / class / order / family / genus is [species] in" / "taxonomy of [organism]" / "show me the lineage of [animal/plant]" / "where does [species] sit in the tree of life" — returns the full classification chain (kingdom → phylum → class → order → family → genus → species) for a Catalogue of Life taxon ID. Use after search to get the lineage of a specific species.

Input Schema

Name	Required	Description	Default
`id`	Yes
`dataset`	No

Output Schema

Name	Required	Description	Default
`count`	Yes	Number of items returned.
`items`	Yes	Taxonomic classification chain from kingdom to species

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedMay 27, 2026

addedInput schema / examples

Added value: +[
+  {
+    "id": "7XCCF"
+  }
+]

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "count": {
+      "description": "Number of items returned.",
+      "type": "integer"
+    },
+    "items": {
+      "description": "Taxonomic classification chain from kingdom to species",
+      "items": {
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "items",
+    "count"
+  ],
+  "type": "object"
+}

First observedMay 14, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, and destructiveHint=false. The description adds context beyond this by specifying the exact output structure (kingdom → phylum → class → order → family → genus → species) and clarifying that the input is a Catalogue of Life taxon ID, which sets expectations for the accepted identifier.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well-structured: it opens with example natural language queries, then states the output and usage note. It is slightly verbose with the example list, but every part serves to help the agent match user intent and understand the tool's role in the workflow.

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?

For a relatively simple read-only lookup tool, the description covers purpose, usage workflow, and the required parameter. The presence of an output schema means the return values need not be fully described, and the description even provides the output lineage chain. The only notable gap is the unexplained optional `dataset` parameter.

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 schema has 0% description coverage, so the description must compensate. It explains the required `id` parameter as a Catalogue of Life taxon ID, but the optional `dataset` parameter is left completely unexplained. The example in the schema shows a sample value but no semantics, so the description only partially covers 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 clearly states the tool returns the full classification chain for a Catalogue of Life taxon ID, using a specific verb and resource. It also includes example queries that make the purpose unmistakable and distinguishes it from the sibling `search` tool by indicating it operates on the output of search.

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

Usage Guidelines5/5

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

The description explicitly says 'Use after `search` to get the lineage of a specific species,' which provides clear workflow guidance and names the alternative tool (search). This gives the agent a concrete condition for when to select this tool.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

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