Skip to main content
Glama

Dataverse Harvard

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Dataverse

dataverse
Read-onlyIdempotent

Dataverse (collection) metadata by alias or id.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
identifierYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataNoDataverse metadata
statusNoAPI response status

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "identifier": "harvard"
+  }
+]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "description": "Dataverse collection metadata",
+  "properties": {
+    "data": {
+      "description": "Dataverse metadata",
+      "properties": {
+        "affiliation": {
+          "description": "Affiliated institution",
+          "type": "string"
+        },
+        "dataverseContacts": {
+          "description": "Contact information",
+          "items": {
+            "type": "object"
+          },
+          "type": "array"
+        },
+        "description": {
+          "description": "Dataverse description",
+          "type": "string"
+        },
+        "id": {
+          "description": "Dataverse ID",
+          "type": "integer"
+        },
+        "identifier": {
+          "description": "Dataverse alias or identifier",
+          "type": "string"
+        },
+        "name": {
+          "description": "Dataverse name",
+          "type": "string"
+        },
+        "type": {
+          "description": "Dataverse type",
+          "type": "string"
+        }
+      },
+      "type": "object"
+    },
+    "status": {
+      "description": "API response status",
+      "type": "string"
+    }
+  },
+  "type": "object"
+}
  2. First observed

TDQS

B3/5.0
Behavior3/5

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

Annotations already provide safety info (read-only, idempotent). The description adds the 'by alias or id' scope but no further behavioral traits. Adequate but minimal extra value.

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?

Single sentence with no filler. Could be considered too minimal but still conveys core purpose efficiently.

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?

Given the output schema exists and the tool is simple, the description is minimally complete. However, it does not explain what a dataverse is or how the identifier relates to the alias/ID distinction.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 0% schema description coverage, the description says the parameter is an alias or ID, but no format or example details beyond the schema's example. Insufficient compensation for missing schema descriptions.

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?

The description clearly states it retrieves metadata for a dataverse (collection) by alias or ID. It is specific enough to distinguish from sibling tools like 'dataset', though it could elaborate on what metadata includes.

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?

No guidance on when to use this tool versus alternatives like 'dataset' or 'search'. Missing when-not scenarios and alternative tool suggestions.

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

All Dataverse Harvard 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