Skip to main content
Glama

guif

by io.github.pipeworx-io
OverviewAdmin

Occurrences Near

occurrences_near
Read-onlyIdempotent

Find species occurrence records NEAR a location (latitude/longitude + radius). PREFER for "what species/wildlife are found near here", "what birds/plants occur around these coordinates", "is recorded near this spot". Optionally filter by a GBIF taxon key (from search_species) to a group or species — e.g. 212 = birds, 6 = plants, 359 = mammals. Returns georeferenced records with species name, date, locality, and source.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum records to return (1-300, default 20).
latitudeYesLatitude in decimal degrees (e.g., 40.785).
longitudeYesLongitude in decimal degrees (e.g., -73.968).
radius_kmNoSearch radius in km (default 10, max 200).
taxon_keyNoOptional GBIF backbone taxon key to restrict to a species or group (e.g., 212 = birds, 6 = plants, 359 = mammals).
taxon_nameNoOptional scientific name to restrict to, e.g. "Danaus plexippus". Resolved to a GBIF backbone taxon key automatically. Alternative to taxon_key.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "latitude": 40.785,
+    "longitude": -73.968
+  },
+  {
+    "latitude": -33.865,
+    "limit": 50,
+    "longitude": 151.209,
+    "radius_km": 25,
+    "taxon_key": 212
+  }
+]
  2. Changed2 schema fields changed
    • changedInput schema / properties / taxon_key / description
      Previous value: -"Optional GBIF taxon key to restrict to a species or group (e.g., 212 = birds). From search_species."New value: +"Optional GBIF backbone taxon key to restrict to a species or group (e.g., 212 = birds, 6 = plants, 359 = mammals)."
    • addedInput schema / properties / taxon_name
      Added value: +{
+  "description": "Optional scientific name to restrict to, e.g. \"Danaus plexippus\". Resolved to a GBIF backbone taxon key automatically. Alternative to taxon_key.",
+  "type": "string"
+}
  3. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and idempotentHint, and describe returns georeferenced records with fields (species name, date, locality, source), adding value beyond the schema. The openWorldHint suggests non-exhaustive results, but the description does not explicitly address that nuance; still, it adds meaningful context for a read-only tool.

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 three sentences, front-loaded with the core purpose, then usage guidance, then return details. Every sentence earns its place with no filler or repetition, making it highly scannable.

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 a 6-parameter tool with no output schema, the description covers purpose, preferred queries, filtering via taxon_key, and return contents. It could explicitly acknowledge the openWorldHint (e.g., that results may not be comprehensive) but overall it is complete enough for an agent to select and invoke the tool correctly.

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%, so the baseline is 3. The description adds examples for taxon_key (212=birds) and mentions the taxon_name alternative indirectly via 'from search_species', but these details are also present in the schema. It reinforces semantics without adding substantial new 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 opens with a specific verb and resource: 'Find species occurrence records NEAR a location (latitude/longitude + radius).' It distinguishes the tool from siblings by using 'PREFER' and giving representative queries ('what species/wildlife are found near here'), which differentiates it from tools like get_occurrences or search_species.

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 names preferred use cases ('PREFER for...') and even gives example phrasings. It also hints at the relationship to search_species ('from search_species') for obtaining a taxon key. It stops short of explicitly naming competing tools or stating when not to use it, but the 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 guif toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources