Skip to main content
Glama

Get References or Citations (with Bibliography Export)

library_citations
Read-onlyIdempotent

Retrieve works cited by a scholarly item or works citing it, using OpenAlex with OpenCitations fallback. Optionally return formatted bibliography in BibTeX, RIS, or APA.

Instructions

List the works a scholarly item cites (direction: "references") or the works that cite it (direction: "citations"), resolved through OpenAlex's citation graph with OpenCitations as a fallback when OpenAlex has no record. Accepts an id/source from library_search or library_ask, or a bare DOI/arXiv id. Set format: "bibtex" | "ris" | "apa" to also return a formatted bibliography string; BibTeX prefers Crossref's own citation when a DOI is resolvable, for the first 20 results only (a paced, one-at-a-time doi.org lookup per item), with later results using a locally generated entry instead. Set response_format: "detailed" for full result fields.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesItem identifier from library_search/library_ask, or a bare DOI/arXiv id
limitNoMax results
formatNoAlso return a `formatted` bibliography string in this style
sourceYesLibrary source name. Run library_list_sources for the current list and descriptions.
directionYesreferences: works this item cites. citations: works that cite this item.
response_formatNoconcise (default) trims results/citations to high-signal fields; detailed returns the full payload, including routing reasons, scores, and stage diagnostics.concise

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
seedYes
resultsYes
directionYes
formattedNo

Schema Changelog

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

  1. First observedv11.0.0

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the readOnly/idempotent annotations, the description discloses OpenAlex-to-OpenCitations fallback behavior, Crossref DOI lookup pacing (one-at-a-time, first 20 only), and what 'detailed' returns including routing reasons and diagnostics. This is substantial behavioral context.

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?

Three sentences front-load the core operation and direction semantics, then pack necessary caveats into later clauses. Every clause adds decision-relevant information with no fluff.

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 description covers identifiers, direction, fallback sources, formatting behavior, response modes, and diagnostics. Combined with the rich schema and output schema, an agent has what it needs to invoke this tool correctly.

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%, but the description adds important cross-parameter meaning: format triggers a formatted bibliography string, BibTeX has special Crossref behavior, and response_format controls field richness. This enriches the schema rather than repeating it.

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 names a specific verb ('List'), the resource (works cited by or citing a scholarly item), and the two directions with clear semantics. It also distinguishes itself from sibling query tools by framing the output as a citation graph operation.

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 clearly signals that this tool is for resolved items, explicitly accepting IDs from library_search or library_ask or a bare DOI/arXiv ID. It explains when to use format and response_format, though it does not explicitly name sibling tools to exclude.

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

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/The-40-Thieves/alexandria-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server