Skip to main content
Glama

crossref

by io.github.pipeworx-io

Get Work

get_work
Read-onlyIdempotent

Get full metadata for a publication by DOI (e.g., "10.1038/nature12373"). Returns title, authors, abstract, journal, publisher, citations, and subjects.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
doiYesDOI of the work (e.g., "10.1038/nature12373")

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
doiYesDigital Object Identifier
urlYesURL to access the work
typeYesWork type (e.g., journal-article, book)
titleYesWork title
authorsYesList of author names
journalYesJournal or container title
abstractYesWork abstract or summary
subjectsYesSubject categories or keywords
citationsYesNumber of citations referencing this work
publishedYesPublication date in YYYY-MM-DD format
publisherYesPublisher name

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.1038/nature12373"
+  }
+]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "abstract": {
+      "description": "Work abstract or summary",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "authors": {
+      "description": "List of author names",
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "citations": {
+      "description": "Number of citations referencing this work",
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "doi": {
+      "description": "Digital Object Identifier",
+      "type": "string"
+    },
+    "journal": {
+      "description": "Journal or container title",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "published": {
+      "description": "Publication date in YYYY-MM-DD format",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "publisher": {
+      "description": "Publisher name",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "subjects": {
+      "description": "Subject categories or keywords",
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "title": {
+      "description": "Work title",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "type": {
+      "description": "Work type (e.g., journal-article, book)",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "url": {
+      "description": "URL to access the work",
+      "type": "string"
+    }
+  },
+  "required": [
+    "doi",
+    "title",
+    "journal",
+    "authors",
+    "published",
+    "type",
+    "publisher",
+    "abstract",
+    "citations",
+    "subjects",
+    "url"
+  ],
+  "type": "object"
+}
  2. Changed2 schema fields changed
    • removedInput schema / examples
      Removed value: -[
-  {
-    "doi": "10.1038/nature12373"
-  }
-]
    • changedOutput schema / (root)
      Previous value: -{
-  "properties": {
-    "abstract": {
-      "description": "Work abstract or summary",
-      "type": [
-        "string",
-        "null"
-      ]
-    },
-    "authors": {
-      "description": "List of author names",
-      "items": {
-        "type": "string"
-      },
-      "type": "array"
-    },
-    "citations": {
-      "description": "Number of citations referencing this work",
-      "type": [
-        "number",
-        "null"
-      ]
-    },
-    "doi": {
-      "description": "Digital Object Identifier",
-      "type": "string"
-    },
-    "journal": {
-      "description": "Journal or container title",
-      "type": [
-        "string",
-        "null"
-      ]
-    },
-    "published": {
-      "description": "Publication date in YYYY-MM-DD format",
-      "type": [
-        "string",
-        "null"
-      ]
-    },
-    "publisher": {
-      "description": "Publisher name",
-      "type": [
-        "string",
-        "null"
-      ]
-    },
-    "subjects": {
-      "description": "Subject categories or keywords",
-      "items": {
-        "type": "string"
-      },
-      "type": "array"
-    },
-    "title": {
-      "description": "Work title",
-      "type": [
-        "string",
-        "null"
-      ]
-    },
-    "type": {
-      "description": "Work type (e.g., journal-article, book)",
-      "type": [
-        "string",
-        "null"
-      ]
-    },
-    "url": {
-      "description": "URL to access the work",
-      "type": "string"
-    }
-  },
-  "required": [
-    "doi",
-    "title",
-    "journal",
-    "authors",
-    "published",
-    "type",
-    "publisher",
-    "abstract",
-    "citations",
-    "subjects",
-    "url"
-  ],
-  "type": "object"
-}New value: +null
  3. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "abstract": {
+      "description": "Work abstract or summary",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "authors": {
+      "description": "List of author names",
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "citations": {
+      "description": "Number of citations referencing this work",
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "doi": {
+      "description": "Digital Object Identifier",
+      "type": "string"
+    },
+    "journal": {
+      "description": "Journal or container title",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "published": {
+      "description": "Publication date in YYYY-MM-DD format",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "publisher": {
+      "description": "Publisher name",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "subjects": {
+      "description": "Subject categories or keywords",
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "title": {
+      "description": "Work title",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "type": {
+      "description": "Work type (e.g., journal-article, book)",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "url": {
+      "description": "URL to access the work",
+      "type": "string"
+    }
+  },
+  "required": [
+    "doi",
+    "title",
+    "journal",
+    "authors",
+    "published",
+    "type",
+    "publisher",
+    "abstract",
+    "citations",
+    "subjects",
+    "url"
+  ],
+  "type": "object"
+}
  4. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "doi": "10.1038/nature12373"
+  }
+]
  5. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare the tool as read-only, idempotent, open-world, and non-destructive. The description adds a concrete DOI example and enumerates the returned fields, which gives behavioral context beyond the safety annotations. No contradiction exists.

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 two sentences, front-loaded with the verb and resource, and contains no redundant or vague wording. It is appropriately concise and well-structured.

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?

The tool is simple with one parameter, rich annotations, and an output schema. The description covers the purpose, the lookup key, and the type of data returned, making it complete for an agent to invoke correctly.

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?

The input schema fully describes the single 'doi' parameter with type, description, and example. The description repeats this example and adds no new parameter-level information, so the baseline 3 applies.

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 uses a specific verb 'Get' with a clear resource 'full metadata for a publication by DOI' and lists returned fields. This distinguishes it from sibling tools like search_works (which searches without a DOI) and get_journal (which targets journals).

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 clearly indicates the use case: retrieving metadata when you have a DOI. It provides a concrete example. However, it does not explicitly mention when not to use it or compare alternatives, so it lacks exclusion guidance.

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

All crossref 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.8/5.0
Disambiguation2/5

Several tools overlap heavily: ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, deep_research, discover_tools, and suggest_questions all serve queries, with ask_pipeworx_beta explicitly identical to ask_pipeworx. Prediction-market tools (polymarket_edges, polymarket_arbitrage, polymarket_fill_risk, bet_research, etc.) also have unclear boundaries, making tool selection tricky for an agent.

Naming Consistency4/5

Tool names are consistently lowercase snake_case with a mostly verb-first pattern (get_work, search_works, list_subscriptions, validate_claim). Minor deviations exist: some names are noun-first (entity_profile, recent_changes) and prefixes vary (get/search/list/ask/scan), but the overall convention is predictable and readable.

Tool Count2/5

34 tools is far too many for a server named 'crossref', and only three tools actually relate to Crossref. The rest form a sprawling utility belt covering data routing, memory, subscriptions, prediction markets, AI visibility, and npm scanning — a scope mismatch that makes the server feel like a kitchen sink rather than a focused offering.

Completeness2/5

The Crossref-specific surface is thin: search_works, get_work, and get_journal cover discovery and metadata but lack citation lookup, author search, and funder information. The broader Pipeworx surface is extensive but has no unifying domain, so it's impossible to consider the overall toolset complete for any coherent purpose.

Resources