Opentreeoflife

Taxon Info

taxon_info

Read-onlyIdempotent

Get full details for an Open Tree of Life taxon by ott_id (from match_names) — accepted name, rank, unique name, synonyms, source taxonomy, and the complete ancestry lineage from this taxon up to the root of life. Keyless.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "ott_id": 770315
    },
    "name": "taxon_info"
  }
}

Input Schema

Name	Required	Description	Default
`ott_id`	Yes	OTT taxon id, e.g. 770315. Get it from match_names.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedJul 29, 2026

addedInput schema / examples

Added value: +[
+  {
+    "ott_id": 770315
+  },
+  {
+    "ott_id": 417950
+  }
+]

First observedJun 11, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already indicate the tool is read-only, idempotent, and non-destructive. The description adds behavioral context: 'Keyless' (no auth needed) and lists the full ancestry lineage. No contradictions.

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, well-structured sentence that efficiently conveys the tool's purpose and output. No unnecessary words 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 no output schema, the description lists all major return fields (accepted name, rank, synonyms, etc.) and the ancestry lineage. It lacks error handling details, but overall completeness is high for a straightforward lookup tool.

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 coverage is 100% with a clear parameter description. The tool description reinforces the source (from match_names) but does not add new parameter semantics beyond the schema. 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 it retrieves full details for an Open Tree of Life taxon, specifying the input source (ott_id from match_names) and listing output fields (accepted name, rank, etc.). It distinguishes from sibling tools like match_names and common_ancestor.

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 ties the ott_id to match_names, guiding users to first use that tool. It does not explicitly state when to avoid this tool or list alternatives, but the prerequisite is clear. 'Keyless' is a minor usage note.

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

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