Skip to main content
Glama

Inaturalist Search Taxa

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

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": {
      "query": "Panthera leo"
    },
    "name": "inaturalist_search_taxa"
  }
}

Input Schema

NameRequiredDescriptionDefault
rankNoRestrict to a rank (kingdom, phylum, class, order, family, genus, species)
queryYesCommon or scientific name
per_pageNoResults per page (1-30, default 10)

Output Schema

NameRequiredDescriptionDefault
resultsYesArray of taxon records
total_resultsYesTotal taxa matching search

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds the result fields an agent will receive, but says nothing about pagination limits, result ordering, empty-result behavior, or how common-name matching differs from scientific-name matching.

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?

Three short sentences, front-loaded with the action and inputs, then the returns, then the follow-up advice. No filler, though the return-field list slightly overlaps the output schema and could have been trimmed.

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?

With a full output schema, complete parameter descriptions, and read-only annotations, the description only needs to orient the agent, which it does. The remaining gap is workflow context: no mention of paging behavior or how to narrow an ambiguous name beyond using rank.

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%, with all three parameters, the rank values, and the per_page range already documented in the schema. The description's '(common or scientific)' restates the query schema text rather than adding matching semantics or syntax. Baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource ('Search iNaturalist taxa by name') and names the accepted input kinds (common or scientific). It is clear enough to separate from observation-oriented siblings, but it never explicitly names or contrasts with search_observations, which is the nearest alternative.

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

Usage Guidelines3/5

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

The sentence 'Use the taxon ID for downstream filters or to disambiguate look-alike species' gives a real usage hint about what to do with results. It does not state when to prefer this tool over searching observations directly, nor any prerequisites or exclusions, so guidance stays implied.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.