Skip to main content
Glama

Datacite

by io.github.pipeworx-io
OverviewDiscussionsAdmin

List Repositories

list_repositories
Read-onlyIdempotent

List DataCite-registered data repositories (e.g., Zenodo, Dryad, Figshare). Filter by query. Useful for "where do I deposit a dataset" lookups.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNo1-based page
queryNoRepository name / description filter
page_sizeNo1-1000 (default 25)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
totalYesTotal number of repositories
returnedYesNumber of repositories returned in this page
repositoriesYesList of data repositories

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "query": "data repository"
+  }
+]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "repositories": {
+      "description": "List of data repositories",
+      "items": {
+        "properties": {
+          "description": {
+            "description": "Repository description",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "domain": {
+            "description": "Domain of the repository",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "id": {
+            "description": "Repository ID",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "name": {
+            "description": "Repository name",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "re3data_url": {
+            "description": "re3data registry URL",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "repository_types": {
+            "description": "Types of repository",
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          },
+          "symbol": {
+            "description": "Repository symbol code",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "url": {
+            "description": "Repository URL",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "year_created": {
+            "description": "Year repository was created",
+            "type": [
+              "number",
+              "null"
+            ]
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "returned": {
+      "description": "Number of repositories returned in this page",
+      "type": "number"
+    },
+    "total": {
+      "description": "Total number of repositories",
+      "type": "number"
+    }
+  },
+  "required": [
+    "total",
+    "returned",
+    "repositories"
+  ],
+  "type": "object"
+}
  2. First observed

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, and destructiveHint=false, covering the safety and behavioral profile. The description adds that repositories are DataCite-registered and support filtering, but no additional behaviors (e.g., pagination details, rate limits) are disclosed. The description adds value but does not significantly expand beyond annotations.

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 extremely concise (two sentences), front-loaded with the main purpose, and includes an example and a use case. No unnecessary words; every sentence earns its place.

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?

Given the low complexity, full schema coverage, and presence of an output schema, the description is fairly complete. It provides examples and a clear use case. However, it could optionally mention pagination behavior (though schema covers defaults) and briefly note the response structure, but the output schema likely covers that. Minor 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 coverage is 100% with each parameter documented (page, query, page_size). The description only mentions 'filter by query' which is redundant with the schema. It adds no new semantics beyond the schema, so baseline 3 is appropriate.

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 clearly states the tool lists DataCite-registered data repositories, provides concrete examples (Zenodo, Dryad, Figshare), and distinguishes itself from sibling tools which are unrelated to repositories. The verb 'list' and resource 'repositories' are specific.

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 says it's useful for 'where do I deposit a dataset' lookups, giving a clear context of use. It does not mention alternatives or when not to use, but sibling tools do not compete, so this is a minor omission. 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 Datacite 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