crossref-mcp-server

Get Reference List

crossref_get_references

Read-onlyIdempotent

Returns the outgoing reference list for a DOI — the works cited by this paper. Each reference includes the deposited citation string and, where Crossref has resolved it, a DOI you can look up with crossref_get_work. Results are paged: referenceCount is the full deposited total, and when more remain the response carries a nextOffset to pass back as offset. Reference list coverage varies by publisher; many older works and non-participating publishers have no indexed references. Incoming citations — the works that cite this paper — are not available through Crossref; use OpenAlex for that.

Input Schema

TableJSON Schema

Name	Required	Description
`doi`	Yes	DOI in the format "10.NNNN/suffix", e.g. "10.1038/nature12373". A resolver-wrapped form — "https://doi.org/10.1038/nature12373", "https://dx.doi.org/…", "doi:10.1038/nature12373" — is accepted and unwrapped.
`limit`	No	Maximum number of references to return in one page (1–500, default 100). Most works fit in a single page; bibliography records can carry tens of thousands.
`offset`	No	Zero-based index of the first reference to return. Pass the nextOffset value from the previous response to continue through a long reference list.

Output Schema

TableJSON Schema

Name	Required	Description
`cap`	No	The limit that was applied to this page.
`doi`	No	DOI of the citing work
`error`	No	Present when the call failed. Absent on success.
`shown`	No	Number of references returned in this page.
`notice`	No	Coverage guidance when no references are indexed, or a range explanation when the requested offset is past the end of the list. Absent on a normal page.
`offset`	No	Zero-based index of the first returned reference within the deposited list
`truncated`	No	True when references remain beyond this page. Absent when the page is the last.
`nextOffset`	No	Offset to pass in the next call to retrieve the following page. Absent when this page reaches the end of the reference list.
`references`	No	Page of the outgoing reference list
`referenceCount`	No	Total number of references in the deposited list

Schema Changelog

Changes observed during successful MCP inspections.

First observedSep 19, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Annotations already declare readOnlyHint and idempotentHint, and the description does not contradict them. It adds valuable behavior beyond annotations: pagination semantics with referenceCount and nextOffset, coverage caveats for older/non-participating publishers, and the explicit statement that incoming citations are not available through Crossref.

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?

Five sentences, all information-dense and free of filler. The primary purpose is front-loaded, followed by output characteristics, pagination, caveats, and alternatives in a logical order. Every sentence earns its place.

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 rich input schema, output schema presence, and readOnly annotations, the description is complete. It covers purpose, pagination behavior, limitations, and alternative tools without needing to restate schema fields or return formats.

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

Parameters4/5

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

Schema coverage is 100%, so the schema carries most parameter meaning. The description adds value by tying offset to the response's nextOffset value, explaining referenceCount as the full deposited total, and noting that most works fit in one page while long bibliographies require paging.

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 states a specific verb and resource: 'Returns the outgoing reference list for a DOI — the works cited by this paper.' It clearly distinguishes the tool from crossref_get_work by saying resolved DOIs can be looked up with that sibling, and it rules out incoming citations explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description tells the agent when to use this tool (for works cited by a paper), identifies crossref_get_work as the follow-up for resolved DOIs, and directs incoming-citation use cases to OpenAlex. It also warns about coverage variability by publisher, preventing false expectations.

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

All crossref-mcp-server tools Inspect

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.