Skip to main content
Glama
Sign In
.

.

by idss-mesa
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

gbif_registry_get_installation

Read-onlyIdempotent

Retrieve complete details for a specific biodiversity data installation by UUID, including endpoints, hosting organization, and datasets served.

Instructions

Get complete details for a specific IPT or data server installation. Returns technical endpoint information, hosting organization, and datasets served by this installation.

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": {
      "key": "<key>"
    },
    "name": "gbif_registry_get_installation"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyYesInstallation UUID. The unique identifier for the installation server. Get from gbif_registry_search_installations.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint, so the safety profile is covered. The description adds real value on top by disclosing what the response contains (technical endpoint information, hosting organization, datasets served), which matters because there is no output schema.

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?

Two tight sentences, zero filler, front-loaded with the action and resource before the return-value detail.

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 single-parameter read with full schema coverage and rich annotations, the description supplies enough; the return-content summary compensates for the absent output schema. It is only slightly thin on how the result differs from a search hit.

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% and the schema already documents the key as a UUID with its source tool, so the baseline is 3. The description adds nothing about the parameter itself.

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 ('Get') and resource ('a specific IPT or data server installation') and even names the returned content. The word 'specific' implicitly separates it from gbif_registry_search_installations, but no sibling is named explicitly, so it falls just short of a 5.

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?

Usage is only implied: the word 'specific' suggests this is the detail-fetch to follow a search, and the schema's key description points to gbif_registry_search_installations. The description itself gives no explicit when-to-use or when-not-to-use guidance.

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