Skip to main content
Glama

crossref-mcp-server

Get Prefix Owner

crossref_get_prefix
Read-onlyIdempotent

Resolves a DOI prefix — the registrant portion of a DOI, e.g. "10.1038" — to the Crossref member its prefix record names: the publisher name and numeric member ID. That member is the prefix's registrant, so for a title transferred to another publisher it is not the member holding the DOI now — crossref_get_work's memberId names that one. The Crossref prefix record carries only these three facts (no counts, coverage, or flags); the returned memberId chains directly into crossref_get_member for the full publisher record.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "prefix": "<prefix>"
    },
    "name": "crossref_get_prefix"
  }
}

Input Schema

NameRequiredDescriptionDefault
prefixYesDOI prefix in the format "10.NNNN" — the registrant portion of a DOI with no "/suffix", e.g. "10.1038" or "10.1371".

Output Schema

NameRequiredDescriptionDefault
errorNoPresent when the call failed. Absent on success.
prefixNoThe DOI prefix that was resolved, e.g. "10.1038"
memberIdNoNumeric Crossref member ID the prefix record names — pass to crossref_get_member for the full publisher record. For a transferred title it is a former publisher; a DOI's current member is the memberId crossref_get_work returns.
ownerNameNoName of the member (publisher) the prefix record names — its registrant

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / properties / error / properties / data / properties / reason / description
      Previous value: -"Machine-readable failure mode. Declared by this tool: `rate_limited`: Crossref answered HTTP 429 and the limit did not clear inside the retry budget. `upstream_unavailable`: Crossref was unreachable, returned a 5xx status, or served an HTML error page instead of JSON. `malformed_response`: Crossref returned HTTP 200 with a body that is not valid JSON, or with facet counts in a shape this server does not read. `request_timeout`: Crossref did not respond within CROSSREF_TIMEOUT_MS, or answered HTTP 408/504. `prefix_not_found`: The DOI prefix is not registered with Crossref. Other values are possible when a failure originates below the handler."New value: +"Machine-readable failure mode. Declared by this tool: `rate_limited`: Crossref answered HTTP 429 and the limit did not clear inside the retry budget, or answered it to the single-attempt published-version lookup on a preprint. `upstream_unavailable`: Crossref was unreachable, returned a 5xx status, or served an HTML error page instead of JSON. `malformed_response`: Crossref returned HTTP 200 with a body that is not valid JSON, or with facet counts in a shape this server does not read. `request_timeout`: Crossref did not respond within CROSSREF_TIMEOUT_MS, did not answer before the 25 s request deadline (CROSSREF_TIMEOUT_MS when longer) that bounds every retry, or answered HTTP 408/504. `prefix_not_found`: The DOI prefix is not registered with Crossref. Other values are possible when a failure originates below the handler."
  2. Changed1 schema field changed
    • changedOutput schema / properties / error / properties / data / properties / reason / description
      Previous value: -"Machine-readable failure mode. Declared by this tool: `rate_limited`: Crossref answered HTTP 429 and the limit did not clear inside the retry budget. `upstream_unavailable`: Crossref was unreachable, returned a 5xx status, or served an HTML error page instead of JSON. `malformed_response`: Crossref returned HTTP 200 with a body that is not valid JSON. `request_timeout`: Crossref did not respond within CROSSREF_TIMEOUT_MS, or answered HTTP 408/504. `prefix_not_found`: The DOI prefix is not registered with Crossref. Other values are possible when a failure originates below the handler."New value: +"Machine-readable failure mode. Declared by this tool: `rate_limited`: Crossref answered HTTP 429 and the limit did not clear inside the retry budget. `upstream_unavailable`: Crossref was unreachable, returned a 5xx status, or served an HTML error page instead of JSON. `malformed_response`: Crossref returned HTTP 200 with a body that is not valid JSON, or with facet counts in a shape this server does not read. `request_timeout`: Crossref did not respond within CROSSREF_TIMEOUT_MS, or answered HTTP 408/504. `prefix_not_found`: The DOI prefix is not registered with Crossref. Other values are possible when a failure originates below the handler."
  3. Changed2 schema fields changed
    • changedOutput schema / properties / memberId / description
      Previous value: -"Numeric Crossref member ID that owns this prefix — pass to crossref_get_member for the full publisher record"New value: +"Numeric Crossref member ID the prefix record names — pass to crossref_get_member for the full publisher record. For a transferred title it is a former publisher; a DOI's current member is the memberId crossref_get_work returns."
    • changedOutput schema / properties / ownerName / description
      Previous value: -"Name of the member (publisher) that owns this prefix"New value: +"Name of the member (publisher) the prefix record names — its registrant"
  4. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint and idempotentHint, so the safety profile is covered. The description adds genuinely useful behavioral context — that the prefix record carries only three facts (no counts, coverage, or flags) and that the named member may be a historical registrant rather than the current one. It stops short of describing error behavior for unregistered prefixes, which is the main remaining unknown.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core resolution statement is front-loaded and there is no filler, but the second half packs three separate ideas (transfer caveat, record contents, chaining) into long em-dash-linked clauses that slow reading. It is dense rather than padded — still, a sentence break or two would improve scanability.

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

Completeness4/5

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

For a one-parameter read tool with annotations and an output schema, the description covers what is needed: what gets resolved, the interpretive caveat about registrant versus current holder, and the natural follow-up call. Return-shape explanation is correctly left to the output schema; only the unregistered-prefix case is unaddressed.

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 coverage is 100% and the single parameter is fully documented, including the '10.NNNN' pattern and the absence of a '/suffix'. The description repeats the example and the 'registrant portion' framing but adds no parsing or normalization detail beyond the schema, so 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?

States a specific verb and resource ('Resolves a DOI prefix ... to the Crossref member its prefix record names') and defines what the prefix is with a concrete example ('10.1038'). It explicitly separates itself from crossref_get_work's memberId, so an agent can tell which tool answers 'who owns this prefix' versus 'who holds this DOI now.'

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?

Gives clear routing context: the returned memberId chains into crossref_get_member, and for transferred titles the current holder must come from crossref_get_work's memberId instead. That is an explicit alternative path for a real edge case, though there is no blanket statement of when to prefer this tool over searching works.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.