crossref

Get Journal

get_journal

Read-onlyIdempotent

Get the 5 most recent works from a journal by ISSN (e.g., "2041-1723"). Returns titles, authors, DOIs, and publication dates.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`issn`	Yes	Journal ISSN (e.g., "1476-4687" for Nature)

Output Schema

TableJSON Schema

Name	Required	Description
`issn`	Yes	Journal ISSN
`recent_works`	Yes	Array of recent works from the journal
`total_results`	Yes	Total number of works in the journal

Schema Changelog

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

Changed2 schema fields changedMay 24, 2026

addedInput schema / examples

Added value: +[
+  {
+    "issn": "1476-4687"
+  }
+]

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "issn": {
+      "description": "Journal ISSN",
+      "type": "string"
+    },
+    "recent_works": {
+      "description": "Array of recent works from the journal",
+      "items": {
+        "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"
+      },
+      "type": "array"
+    },
+    "total_results": {
+      "description": "Total number of works in the journal",
+      "type": "number"
+    }
+  },
+  "required": [
+    "issn",
+    "total_results",
+    "recent_works"
+  ],
+  "type": "object"
+}

Changed2 schema fields changedMay 13, 2026

removedInput schema / examples

Removed value: -[
-  {
-    "issn": "1476-4687"
-  }
-]

changedOutput schema / (root)

Previous value: -{
-  "properties": {
-    "issn": {
-      "description": "Journal ISSN",
-      "type": "string"
-    },
-    "recent_works": {
-      "description": "Array of recent works from the journal",
-      "items": {
-        "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"
-      },
-      "type": "array"
-    },
-    "total_results": {
-      "description": "Total number of works in the journal",
-      "type": "number"
-    }
-  },
-  "required": [
-    "issn",
-    "total_results",
-    "recent_works"
-  ],
-  "type": "object"
-}New value: +null

Changed1 schema field changedMay 8, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "issn": {
+      "description": "Journal ISSN",
+      "type": "string"
+    },
+    "recent_works": {
+      "description": "Array of recent works from the journal",
+      "items": {
+        "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"
+      },
+      "type": "array"
+    },
+    "total_results": {
+      "description": "Total number of works in the journal",
+      "type": "number"
+    }
+  },
+  "required": [
+    "issn",
+    "total_results",
+    "recent_works"
+  ],
+  "type": "object"
+}

Changed1 schema field changedMay 6, 2026
- addedInput schema / examples
```
Added value: +[
+  {
+    "issn": "1476-4687"
+  }
+]
```
First observedApr 14, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint false. The description adds behavioral context beyond this by specifying the result limit ('5 most recent works') and the fields returned (titles, authors, DOIs, publication dates), which are useful for the agent's expectations.

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 core action and scope. Every word contributes value, with an example ISSN and a clear list of returned fields. No fluff or redundancy.

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, an output schema exists, and annotations provide safety profile. The description adequately covers the purpose, result set size, and returned fields, 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 schema provides 100% coverage for the only parameter 'issn' with a description and example. The description reinforces the ISSN-based lookup but does not add new semantic detail beyond the schema. Baseline 3 is appropriate given high schema coverage.

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's function: 'Get the 5 most recent works from a journal by ISSN'. It specifies the verb, resource type (works), and input identifier (ISSN), and the scope (5 most recent). This distinguishes it from siblings like get_work (single work) and search_works (broad search).

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 gives a clear context for use: obtaining recent journal works via ISSN. It does not explicitly mention alternatives or exclusionary cases, but the specificity of the use case provides sufficient guidance for when to select this tool among the siblings.

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

All crossref tools Inspect

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.

Get Journal

Input Schema

Output Schema

Schema Changelog

TDQS

Glama MCP Gateway

TDQS

Resources