Skip to main content
Glama

Datacite

by io.github.pipeworx-io

Get Doi

get_doi
Read-onlyIdempotent

Fetch a single DOI record. Returns full metadata: title(s), creators with affiliations and ORCIDs, abstract, publisher, year, dates, related identifiers, subjects, license, sizes/formats.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
doiYesDOI (e.g., "10.5281/zenodo.1234567")

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
doiYesDigital Object Identifier
urlYesURL to the resource
yearYesPublication year
datesYesImportant dates
sizesYesResource sizes
titleYesPrimary title of the resource
rightsYesRights and licenses
titlesYesAll titles with language tags
formatsYesResource file formats
relatedYesRelated identifiers
updatedYesLast update date
creatorsYesList of creator names
subjectsYesSubject keywords and classifications
publisherYesPublisher name
registeredYesRegistration date
view_countYesNumber of views
datacite_urlYesURL to DataCite commons page
descriptionsYesDescriptions with types
creators_fullYesFull creator details with affiliations and ORCIDs
resource_typeYesGeneral resource type
citation_countYesNumber of citations
download_countYesNumber of downloads

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "doi": "10.5281/zenodo.1234567"
+  }
+]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "citation_count": {
+      "description": "Number of citations",
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "creators": {
+      "description": "List of creator names",
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "creators_full": {
+      "description": "Full creator details with affiliations and ORCIDs",
+      "items": {
+        "properties": {
+          "affiliations": {
+            "description": "Creator affiliations",
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          },
+          "name": {
+            "description": "Creator name",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "orcid": {
+            "description": "ORCID identifier if available",
+            "type": [
+              "string",
+              "null"
+            ]
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "datacite_url": {
+      "description": "URL to DataCite commons page",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "dates": {
+      "description": "Important dates",
+      "items": {
+        "properties": {
+          "date": {
+            "description": "ISO date string",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "type": {
+            "description": "Date type (Created, Updated, etc.)",
+            "type": [
+              "string",
+              "null"
+            ]
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "descriptions": {
+      "description": "Descriptions with types",
+      "items": {
+        "properties": {
+          "text": {
+            "description": "Description text",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "type": {
+            "description": "Description type (Abstract, etc.)",
+            "type": [
+              "string",
+              "null"
+            ]
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "doi": {
+      "description": "Digital Object Identifier",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "download_count": {
+      "description": "Number of downloads",
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "formats": {
+      "description": "Resource file formats",
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "publisher": {
+      "description": "Publisher name",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "registered": {
+      "description": "Registration date",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "related": {
+      "description": "Related identifiers",
+      "items": {
+        "properties": {
+          "id": {
+            "description": "Related identifier",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "relation": {
+            "description": "Relation type",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "type": {
+            "description": "Identifier type",
+            "type": [
+              "string",
+              "null"
+            ]
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "resource_type": {
+      "description": "General resource type",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "rights": {
+      "description": "Rights and licenses",
+      "items": {
+        "properties": {
+          "name": {
+            "description": "License or rights name",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "uri": {
+            "description": "License URI",
+            "type": [
+              "string",
+              "null"
+            ]
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "sizes": {
+      "description": "Resource sizes",
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "subjects": {
+      "description": "Subject keywords and classifications",
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "title": {
+      "description": "Primary title of the resource",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "titles": {
+      "description": "All titles with language tags",
+      "items": {
+        "properties": {
+          "lang": {
+            "description": "Language code",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "title": {
+            "description": "Title text",
+            "type": [
+              "string",
+              "null"
+            ]
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "updated": {
+      "description": "Last update date",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "url": {
+      "description": "URL to the resource",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "view_count": {
+      "description": "Number of views",
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "year": {
+      "description": "Publication year",
+      "type": [
+        "number",
+        "null"
+      ]
+    }
+  },
+  "required": [
+    "doi",
+    "title",
+    "creators",
+    "publisher",
+    "year",
+    "resource_type",
+    "url",
+    "citation_count",
+    "download_count",
+    "view_count",
+    "datacite_url",
+    "titles",
+    "creators_full",
+    "subjects",
+    "descriptions",
+    "dates",
+    "sizes",
+    "formats",
+    "rights",
+    "related",
+    "registered",
+    "updated"
+  ],
+  "type": "object"
+}
  2. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already indicate read-only, idempotent, non-destructive behavior. Description adds detail on returned metadata fields, consistent with 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?

Two sentences: first states action, second lists return fields. No wasted words.

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

Completeness5/5

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

Given the simple tool with one parameter, output schema present, and comprehensive annotations, the description thoroughly covers purpose and returns.

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 already describes the 'doi' parameter with an example. Description adds no additional semantic detail beyond the schema.

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?

Clearly states it fetches a single DOI record and lists specific metadata returned, distinguishing it from 'search_dois' for multiple records.

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?

Explicitly describes fetching a single record, implying usage when a specific DOI is known, but does not explicitly contrast with sibling 'search_dois'.

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
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.7/5.0
Disambiguation2/5

Several tools occupy overlapping roles: ask_pipeworx, ask_pipeworx_beta, and ask_pipeworx_grounded are near-identical entry points (beta currently behaves exactly like stable), while entity_profile, recent_changes, and compare_entities all target company research. The prediction-market cluster (bet_research, polymarket_edges, polymarket_arbitrage, polymarket_edge_tracker, polymarket_fill_risk, polymarket_kalshi_spread) is large enough that an agent could easily select the wrong one.

Naming Consistency2/5

Naming conventions are mixed throughout: verb_noun patterns (search_dois, list_repositories, validate_claim) coexist with noun phrases (entity_profile, recent_alerts, ai_visibility_check) and bare verbs (remember, recall, forget, subscribe). The only consistent thread is snake_case, but the grammatical style is unpredictable.

Tool Count2/5

At 34 tools, the server is overstuffed, especially given its apparent focus is DataCite but only 3 tools actually serve that domain (get_doi, search_dois, list_repositories). The rest are a grab bag of Pipeworx data routing, prediction-market analytics, memory, and subscription utilities that would be better split into separate focused servers.

Completeness2/5

The DataCite surface is incomplete (no DOI creation, update, or deletion despite DataCite supporting registration), while the Pipeworx surface has no direct fetch-by-URI tool for the pipeworx:// citations that other tools return. The presence of a duplicate beta router and a beta router with no active differences further muddies the coverage picture.

Resources