Skip to main content
Glama

inaturalist-mcp-server

Inaturalist Get Species Counts

inaturalist_get_species_counts
Read-only

Rank the distinct species recorded in an area and period, most-observed first — the "what lives here" answer, without paging through individual sightings. An area is given in exactly one form: place_id, the lat/lng/radius triple in kilometres, or a four-corner bounding box. Narrow to a clade by passing taxon_id, e.g. the birds of a park. Defaults to research-grade, wild-only records and echoes those defaults back. For the most active people rather than the most recorded species, use inaturalist_get_leaderboard.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
d1NoEarliest observation date, YYYY-MM-DD. Inclusive.
d2NoLatest observation date, YYYY-MM-DD. Inclusive.
latNoLatitude of the search centre, in decimal degrees. Requires lng and radius.
lngNoLongitude of the search centre, in decimal degrees. Requires lat and radius.
pageNoPage number. Defaults to 1.
nelatNoNorth-east corner latitude of the bounding box. All four corners or none.
nelngNoNorth-east corner longitude of the bounding box. All four corners or none.
swlatNoSouth-west corner latitude of the bounding box. All four corners or none.
swlngNoSouth-west corner longitude of the bounding box. All four corners or none.
radiusNoSearch radius around lat/lng, in KILOMETRES. Requires lat and lng. The upstream publishes no bound; 500 is a verified ceiling this server imposes.
captiveNoWhether to include captive and cultivated records — zoo animals, garden plantings. Defaults to wild organisms only.
term_idNoAnnotation attribute ids, from inaturalist_list_reference topic controlled_terms — e.g. 1 for Life Stage.
per_pageNoSpecies per page, maximum 50. A ranked species costs roughly 860 bytes across structuredContent and the rendered text together, so 50 is a full page near 43 KB. Upstream would serve 500 in one page — raise page rather than asking for it.
place_idNoNumeric iNaturalist place id from inaturalist_find_places. Mutually exclusive with the lat/lng/radius triple and the bounding box. A non-numeric value answers HTTP 500 upstream.
taxon_idNoRestrict to this taxon and its descendants. Resolve a name to an id with inaturalist_resolve_name.
iconic_taxaNoBroad organism groups, by their scientific iconic-taxon name. A common-name value such as "Birds" matches nothing upstream, so only the listed values are accepted.
quality_gradeNoIdentification confidence tiers to include. Defaults to research-grade only; adding "needs_id" roughly doubles the corpus and lowers identification confidence.
term_value_idNoAnnotation value ids, from the same attribute listing — e.g. 6 for Larva. Requires term_id; sent alone it is ignored upstream and the unfiltered corpus comes back.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
capNoThe per_page that was applied.
errorNoPresent when the call failed. Absent on success.
shownNoHow many species this page carries.
noticeNoGuidance when nothing matched, or how to reach the species beyond this page.
speciesNoThe species, ranked by observation_count, most-observed first.
truncatedNoTrue when the page filled per_page and more species follow.
total_resultsNoHow many distinct species match. An estimate over a live index — it drifts between calls seconds apart.
applied_filtersNoThe server-applied defaults that determine what this answer means.
truncationCeilingNoObservation count of the last species shown. The ranking is descending, so no species left off this page exceeds it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

The annotations only convey read-only and open-world behavior, so the description adds value by disclosing aggregation semantics, research-grade/wild defaults, and the mutually exclusive area-selector rule. It doesn't mention error cases or rate limits, but for a read-only tool the core behavioral context is 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?

Three sentences, each earning its place: the first states the core behavior, the second covers area-parameter constraints, and the third covers filters/defaults plus the leaderboard alternative. It is compact, front-loaded, and free of filler.

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 an 18-parameter tool, the description plus fully documented schema and output schema cover invocation well: area forms, defaults, clade narrowing, and a sibling pointer are all present. It does not explicitly state what happens if no area selector is supplied, and it only names one of several nearby siblings, so it is strong but not exhaustive.

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%, so the baseline applies and the schema already explains each parameter in detail. The description adds useful high-level framing such as the three mutually exclusive area forms and a concrete taxon example, but it doesn't materially expand individual parameter meaning beyond the schema.

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 names a specific, informative verb+resource pair: it ranks distinct species in an area by observation count. It also clearly distinguishes itself from paginating individual sightings and from the leaderboard sibling, so an agent can tell what the tool does at a glance.

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?

It explicitly states that the area must be given in exactly one of three forms, how to narrow by clade, and what the default filtering is. It also names the sibling tool to use when ranking people rather than species, giving a concrete when-not-to-use case.

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.