Skip to main content
Glama

Cite from a DOI

cite_from_doi
Read-only

Look up a DOI on Crossref and generate a formatted citation in APA, MLA, Chicago, Harvard, IEEE, BibTeX, RIS, or all styles at once.

Instructions

Look up a DOI on Crossref and format the citation. The Crossref record decides the shape: a journal article, a book or an edited book, a book chapter or a conference paper, a thesis, a report, a dataset or a preprint. Inputs: doi (a DOI like 10.1038/nature14539 or a doi.org link) and style (apa7, mla9, chicago-ad, harvard, ieee, bibtex or all). Pass all to get all three styles in one reply, each one with its style name on the line above it. Pass bibtex to get one .bib entry for a reference manager. Example prompt: "Cite 10.1038/nature14539 in APA." For BibTeX, ask "Give me BibTeX for this DOI: 10.1038/nature14539."

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": "cite_from_doi"
  }
}

Input Schema

NameRequiredDescriptionDefault
doiYesA DOI like 10.1038/nature14539, or a doi.org link.
styleNoCitation style. Aliases such as APA, MLA 9 and Chicago are accepted. Valid styles: apa7, mla9, chicago-ad (Chicago author date), harvard, ieee, bibtex and ris (a .ris record for Zotero, EndNote and Mendeley), or all to get APA 7, MLA 9 and Chicago author date in one reply with a label above each one.apa7

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.8
    • changedInput schema / properties / style / description
      Previous value: -"Citation style. Aliases such as APA, MLA 9 and Chicago are accepted. Valid styles: apa7, mla9, chicago-ad (Chicago author date), harvard, ieee and bibtex, or all to get APA 7, MLA 9 and Chicago author date in one reply with a label above each one."New value: +"Citation style. Aliases such as APA, MLA 9 and Chicago are accepted. Valid styles: apa7, mla9, chicago-ad (Chicago author date), harvard, ieee, bibtex and ris (a .ris record for Zotero, EndNote and Mendeley), or all to get APA 7, MLA 9 and Chicago author date in one reply with a label above each one."
  2. Changed1 schema field changedv0.1.7
    • changedInput schema / properties / style / description
      Previous value: -"Citation style. Aliases such as APA, MLA 9 and Chicago are accepted. Valid styles: apa7, mla9, chicago-ad (Chicago author date), harvard and ieee, or all to get APA 7, MLA 9 and Chicago author date in one reply with a label above each one."New value: +"Citation style. Aliases such as APA, MLA 9 and Chicago are accepted. Valid styles: apa7, mla9, chicago-ad (Chicago author date), harvard, ieee and bibtex, or all to get APA 7, MLA 9 and Chicago author date in one reply with a label above each one."
  3. Changed1 schema field changedv0.1.6
    • changedInput schema / properties / style / description
      Previous value: -"Citation style. Aliases such as APA, MLA 9 and Chicago are accepted. Valid styles: apa7, mla9, chicago-ad (Chicago author date)."New value: +"Citation style. Aliases such as APA, MLA 9 and Chicago are accepted. Valid styles: apa7, mla9, chicago-ad (Chicago author date), harvard and ieee, or all to get APA 7, MLA 9 and Chicago author date in one reply with a label above each one."
  4. First observedv0.1.3

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so this is a known-safe external lookup. The description adds real value on top: the result shape is determined by the Crossref record type, and multi-style output is laid out with the style name on the line above each entry. Auth, rate limits, and failure behavior on unknown DOIs are unaddressed.

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?

Purpose and Crossref-dependent output shape come first, then parameters, then modes, then examples — a sensible front-loaded order. The two example prompts at the end are marginally redundant with the preceding sentences but demonstrate realistic invocation phrasing.

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 carries the burden of describing returns and does so for both single-style and 'all' modes, plus the BibTeX special case. The 'ris' omission and lack of error behavior for unresolvable DOIs are the remaining gaps.

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 the schema already documents both parameters, making 3 the baseline. The description adds example prompts and the 'all' vs 'bibtex' distinction, but its style list omits 'ris', which the schema documents — a minor inconsistency that prevents credit above baseline.

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 chain (look up a DOI on Crossref and format the citation) and enumerates the record shapes it can produce. The DOI-specific scope implicitly separates it from cite_from_url, cite_from_arxiv, and cite_from_isbn siblings.

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 context for invocation (DOI in hand, optional style selection) and explicit instructions for special modes: pass 'all' for three styles, pass 'bibtex' for a .bib entry. It never names an alternative sibling or states when-not to use it, which keeps it short of a 5.

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