Skip to main content
Glama

crossref_doi

Retrieve Crossref DOI metadata—including title, authors, publisher, dates, citations, and optional references—to verify or enrich scholarly records.

Instructions

DOI metadata from Crossref: type, title, container (journal/book), publisher, authors with ORCID and affiliations, dates, volume/issue/pages, ISSN/ISBN, licenses, abstract, subjects, citation counts, funders, and optionally the reference list. Costs 0.002 USDC on Base per successful call (x402). Without a payment key this tool returns the 402 challenge.

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": {
      "doi": "<doi>"
    },
    "name": "crossref_doi"
  }
}

Input Schema

NameRequiredDescriptionDefault
doiYesDOI or doi.org URL
referencesNotrue to include references

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.0

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations, the description carries the full burden, and it does substantial work: it discloses the per-call cost (0.002 USDC on Base via x402) and the exact failure mode without a payment key (402 challenge). It does not describe behavior for invalid or not-found DOIs, rate limits, or whether results are cached, which keeps it below a 5.

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

Conciseness4/5

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

The return-field inventory is long but front-loaded and earns its place by letting an agent judge whether the call supplies needed data. The payment and 402 sentences follow efficiently with no filler.

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?

With no output schema, the description correctly compensates by listing returned fields, and it covers the payment/auth model that would otherwise blindside an agent. Only error paths for malformed or unknown DOIs are missing, which is a minor gap for a two-parameter lookup tool.

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%, so both parameters are already documented, establishing a baseline of 3. The description adds marginal value by confirming that the reference list is optional rather than default, but it does not clarify the unusual string typing of the 'references' flag or DOI format handling beyond what the schema states.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names the resource (DOI metadata from Crossref) and enumerates the exact fields returned, so an agent knows precisely what it gets back. It lacks an explicit verb like 'fetch' or 'look up,' but 'DOI metadata from Crossref' is specific enough to distinguish it from siblings such as arxiv_search or isbn_validate.

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

Usage Guidelines3/5

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

It states a real precondition for use — a payment key is required or the call returns a 402 challenge — which is genuinely useful guidance. However, it gives no when-to-use/when-not guidance relative to alternatives (e.g., when to prefer a different metadata source) and no exclusions.

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