Inaturalist

Search Taxa

search_taxa

Read-onlyIdempotent

Search iNaturalist taxa by name (common or scientific). Returns taxon ID, rank, ancestry, conservation status, and photo URL. Use the taxon ID for downstream filters or to disambiguate look-alike species.

Input Schema

TableJSON Schema

Name	Required	Description
`rank`	No	Restrict to a rank (kingdom, phylum, class, order, family, genus, species)
`query`	Yes	Common or scientific name
`per_page`	No	Results per page (1-30, default 10)

Output Schema

TableJSON Schema

Name	Required	Description	Default
`results`	Yes	Array of taxon records
`total_results`	Yes	Total taxa matching search

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedMay 22, 2026

addedInput schema / examples

Added value: +[
+  {
+    "query": "Panthera leo"
+  },
+  {
+    "query": "red panda",
+    "rank": "species"
+  }
+]

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "results": {
+      "description": "Array of taxon records",
+      "items": {
+        "properties": {
+          "ancestry": {
+            "description": "Taxonomic ancestry chain",
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          },
+          "common_name": {
+            "description": "Common name",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "conservation_status": {
+            "description": "IUCN conservation status",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "id": {
+            "description": "Taxon ID",
+            "type": "number"
+          },
+          "observations_count": {
+            "description": "Total observations for taxon",
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "photo": {
+            "description": "Photo URL",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "rank": {
+            "description": "Taxonomic rank",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "scientific_name": {
+            "description": "Scientific name",
+            "type": [
+              "string",
+              "null"
+            ]
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "total_results": {
+      "description": "Total taxa matching search",
+      "type": "number"
+    }
+  },
+  "required": [
+    "total_results",
+    "results"
+  ],
+  "type": "object"
+}

First observedMay 11, 2026

TDQS

A4.1/5.0

Behavior3/5

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

Annotations already declare read-only, idempotent, and non-destructive behavior. The description adds return field details but no behavioral traits beyond what annotations provide.

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?

Two sentences, front-loaded with action and return fields, no waste. Every word adds value.

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?

Covers purpose, return format, and downstream usage. Output schema exists for detail, and parameters are fully described in the schema. No gaps identified.

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 descriptions for all parameters. The description does not add additional meaning beyond what is in the schema, so baseline score of 3 applies.

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 searches iNaturalist taxa by name (common or scientific), lists specific return fields, and distinguishes it from other tools like search_observations by mentioning downstream use of taxon ID.

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?

Provides explicit guidance on using the taxon ID for downstream filters or disambiguation, but does not mention when not to use this tool or direct alternatives among siblings.

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

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