Skip to main content
Glama
Sign In
.

.

by idss-mesa
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

gbif_registry_organization_datasets

Read-onlyIdempotent

List every dataset published by a specific organization to inspect its complete catalog and understand its data contributions and portfolio.

Instructions

List all datasets published by a specific organization. Shows the complete catalog of datasets contributed by an institution. Useful for understanding an organization's data contributions and portfolio.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "organizationKey": "<organizationKey>"
    },
    "name": "gbif_registry_organization_datasets"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNoFilter datasets by type. OCCURRENCE (specimen/observation records), CHECKLIST (species lists), SAMPLING_EVENT (survey data), METADATA (descriptions only). Omit to get all types.
limitNoMaximum number of datasets to return per page. Range: 1-1000, default: 20.
offsetNoPagination offset. Number of datasets to skip. Default: 0.
organizationKeyYesOrganization UUID. The unique identifier of the publishing organization. Example: "07f617d0-c688-11d8-bf62-b8a03c50a862". Get from gbif_registry_search_organizations or gbif_registry_get_organization.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

B3.1/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 only a mild scope claim ('complete catalog') but says nothing about pagination behavior, result volume, or what happens with very large publishers, so it does not meaningfully extend the annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the core action, which is good, but the second and third sentences restate the same idea twice ('complete catalog of datasets contributed by an institution' / 'useful for understanding an organization's data contributions and portfolio'), so two of three sentences are largely redundant padding.

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?

There is no output schema, yet the description does not indicate what a returned dataset entry contains, and parameter behavior is left entirely to the schema. For a simple read/list tool with full schema coverage this is adequate but leaves the agent with no picture of the response shape.

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%: the enum values for type, the range/default for limit and offset, and the UUID format plus source tools for organizationKey are all documented inline. The description adds no additional parameter meaning, so the 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?

States a specific verb (List) and resource (datasets) with a clear scope qualifier (published by a specific organization), so an agent can distinguish it from the generic gbif_registry_search_datasets. However, it never names or routes against siblings like gbif_registry_search_datasets, gbif_registry_get_organization, or gbif_registry_network_datasets, which is the classic 'clear but no sibling differentiation' case.

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

Usage Guidelines2/5

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

'Useful for understanding an organization's data contributions and portfolio' gestures at a use case but gives no when-to-use condition, no exclusions, and no alternative tools (e.g., use search_datasets instead when organization is unknown). Nothing tells an agent when this tool is the wrong choice.

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