Skip to main content
Glama

inaturalist-mcp-server

by io.github.cyanheads
OverviewDiscussionsAdmin

Inaturalist Find Places

inaturalist_find_places
Read-only

Resolve a place name to a place id, or list the places containing a map area. Pass q to match a place-name PREFIX, or all four of nelat, nelng, swlat and swlng to list every place covering that box — exactly one of the two, never both. Each result carries the bounding box, place type, and containment chain an area search needs. Place geometry is stripped: a single nearby response carries 247 KB of boundary polygons upstream, none of which reaches the caller.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qNoPlace-name prefix to search. Matches the start of a name, not words inside it. Mutually exclusive with the bounding box.
nelatNoNorth-east corner latitude of the map area, at or north of swlat. All four corners or none.
nelngNoNorth-east corner longitude of the map area. All four corners or none. West of swlng is accepted: it describes a box crossing the antimeridian.
swlatNoSouth-west corner latitude of the map area. All four corners or none.
swlngNoSouth-west corner longitude of the map area. All four corners or none.
per_pageNoMaximum places per list. Honoured on the bounding-box arm only, where it bounds the standard and community lists separately, so up to twice this many places come back. The name-prefix endpoint publishes no page size and returns a fixed page.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
capNoThe most places this response could carry — per_page × 2 on the bounding-box arm, where per_page bounds each list separately; the fixed page upstream served on the name-prefix arm.
errorNoPresent when the call failed. Absent on success.
shownNoHow many places this response carries.
noticeNoGuidance when nothing matched, or when the page capped the result set.
placesNoName-prefix matches. Present on the q arm.
standardNoCurated administrative places covering the area. Present on the bounding-box arm.
communityNoMember-created places covering the area. Present on the bounding-box arm.
truncatedNoTrue when more places may exist than were returned — on the bounding-box arm, when the standard or community list reached per_page.
totalCountNoPlaces upstream reports. On the name-prefix arm, every match before the fixed page; on the bounding-box arm, only the places returned (standard plus community), so it is bounded by the page size rather than a full count.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changed
    • changedInput schema / properties / nelat / description
      Previous value: -"North-east corner latitude of the map area. All four corners or none."New value: +"North-east corner latitude of the map area, at or north of swlat. All four corners or none."
    • changedInput schema / properties / nelng / description
      Previous value: -"North-east corner longitude of the map area. All four corners or none."New value: +"North-east corner longitude of the map area. All four corners or none. West of swlng is accepted: it describes a box crossing the antimeridian."
    • changedInput schema / properties / per_page / description
      Previous value: -"Maximum places to return. Honoured on the bounding-box arm only — the name-prefix endpoint publishes no page size and returns a fixed page."New value: +"Maximum places per list. Honoured on the bounding-box arm only, where it bounds the standard and community lists separately, so up to twice this many places come back. The name-prefix endpoint publishes no page size and returns a fixed page."
    • changedOutput schema / properties / cap / description
      Previous value: -"The page size that bounded this response — per_page on the bounding-box arm, the fixed page upstream served on the name-prefix arm."New value: +"The most places this response could carry — per_page × 2 on the bounding-box arm, where per_page bounds each list separately; the fixed page upstream served on the name-prefix arm."
    • changedOutput schema / properties / error / properties / data / properties / reason / description
      Previous value: -"Machine-readable failure mode. Declared by this tool: `invalid_geography`: Neither q nor a complete bounding box was given, or both were. Other values are possible when a failure originates below the handler."New value: +"Machine-readable failure mode. Declared by this tool: `invalid_geography`: Neither q nor a complete bounding box was given, both were, or the box has nelat south of swlat. Other values are possible when a failure originates below the handler."
    • changedOutput schema / properties / totalCount / description
      Previous value: -"Total places upstream matched, before any page limit."New value: +"Places upstream reports. On the name-prefix arm, every match before the fixed page; on the bounding-box arm, only the places returned (standard plus community), so it is bounded by the page size rather than a full count."
    • changedOutput schema / properties / truncated / description
      Previous value: -"True when more places matched than were returned."New value: +"True when more places may exist than were returned — on the bounding-box arm, when the standard or community list reached per_page."
  2. First observed

TDQS

A4.7/5.0
Behavior5/5

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

With only readOnlyHint and openWorldHint annotations, the description carries the behavioral burden and does so richly: it discloses prefix matching, antimeridian handling, the per_page double-list behavior, and that geometry is stripped with a concrete payload-size example. None of this is available from annotations alone.

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 compact and front-loaded with the primary purpose, then efficiently covers the two modes, output contents, and an important performance behavior. Every sentence contributes information; there is no filler or repetition of schema details.

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?

For a tool with two modes, six parameters, an output schema, and read-only annotations, the description is complete enough for an agent to invoke it correctly. It explains the constraint that exactly one mode must be used, what results contain, and a notable payload optimization, leaving no critical gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds meaning beyond the schema by framing q and the four corners as mutually exclusive modes and clarifying that all four corners must be supplied together. It also adds context around per_page applying only to the bounding-box arm, which is valuable semantic guidance.

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 states a specific verb and resource: resolving a place name to a place id or listing places covering a map area. It clearly distinguishes the two operational modes and gives the criteria for each, which is enough to tell this tool apart from siblings.

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?

It explicitly explains when to pass q versus the four bounding-box coordinates, and warns that exactly one mode must be used, never both. It does not name sibling alternatives or say when to prefer this tool over them, but the internal usage guidance is clear and actionable.

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

All inaturalist-mcp-server toolsInspect
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.

Resources