Skip to main content
Glama
tyson-swetnam

gbif-mcp

by tyson-swetnam
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Remote

gbif_registry_search_datasets

Read-onlyIdempotent

Search the GBIF registry to find published datasets by type, keyword, publisher, country, or coverage, helping you discover data sources and inspect metadata.

Instructions

Search for datasets in the GBIF registry. Find published datasets by type, keyword, publisher, geographic coverage, and taxonomic scope. Essential for discovering data sources and understanding dataset metadata.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qNoFree text search query across dataset title, description, and metadata. Searches in dataset titles, descriptions, keywords, and publishing organization names. Example: "birds", "reef fish", "herbarium specimens".
typeNoDataset type filter. OCCURRENCE (observation/specimen records with coordinates and dates), CHECKLIST (species lists without occurrences), SAMPLING_EVENT (structured surveys with effort data), METADATA (dataset descriptions only). Most common: OCCURRENCE.
limitNoMaximum number of datasets to return per page. Range: 1-1000, default: 20. Use with offset for pagination through large result sets.
decadeNoFilter by decade of temporal coverage. Format: "1980,1990" for data from the 1980s and 1990s. Filters datasets by the decade their occurrence records cover, not publication date.
offsetNoPagination offset. Number of results to skip. A limit of 20 and offset of 40 will get the third page. Default: 0. Maximum offset varies by endpoint.
keywordNoFilter by dataset keyword. Keywords are controlled vocabulary terms assigned to datasets. Example: "bird", "invasive species", "endangered species". Case-insensitive.
hostingOrgNoFilter by hosting organization UUID. The organization that hosts the data infrastructure (may differ from publisher). Example: UUID of a data center or aggregator.
publishingOrgNoFilter by publishing organization UUID. Returns datasets published by a specific organization. Get organization UUIDs from gbif_registry_search_organizations. Example: "07f617d0-c688-11d8-bf62-b8a03c50a862" (GBIF Secretariat).
publishingCountryNoFilter by publishing organization country. 2-letter ISO country code. Example: "US" (United States), "GB" (United Kingdom), "BR" (Brazil). Returns datasets published by organizations in that country.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, openWorld, and non-destructive behavior, so the safety profile is covered. The description adds one useful behavioral detail — that only *published* datasets are returned — but says nothing about result caps, pagination limits, or response shape. A 3 is appropriate against a strong annotation set.

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 tight sentences with the core action front-loaded and zero filler. The final sentence is somewhat soft ('Essential for...') but not wasteful enough to drop below 4.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Nine parameters are fully documented in the schema, but with no output schema the description carries some burden for explaining returns and it stays silent on result structure, total counts, and pagination behavior beyond what the limit/offset schema params imply. Adequate but with a visible gap.

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 schema already documents all nine parameters in detail; baseline 3 applies. The description's filter list adds no syntax or format detail beyond the schema, and its mention of 'taxonomic scope' corresponds to no actual parameter, which is mildly imprecise.

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?

States a specific verb and resource: 'Search for datasets in the GBIF registry,' and names the filtering dimensions. It is clearly distinguishable from gbif_registry_get_dataset (single fetch) and gbif_registry_dataset_metrics, though it never names those siblings explicitly.

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?

'Essential for discovering data sources' implies a discovery use case but gives no explicit when-to-use/when-not guidance, no mention of the alternative get_dataset for full metadata, and no prerequisites. Usage is inferable but not stated.

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

Deploy Server

Other Tools