Skip to main content
Glama

Format a works cited list

format_bibliography
Read-only

Compile multiple sources into one alphabetized works cited list or BibTeX/RIS block across APA 7, MLA 9, Chicago, Harvard and IEEE, with optional DOI, ISBN and URL lookups.

Instructions

Format several sources at once as one works cited list, alphabetised by the first author's family name in APA 7, MLA 9, Chicago author date or Harvard, numbered in citation order in IEEE, or as one BibTeX block or one RIS block in the order you give the sources. A source with no author is alphabetised by its title. Inputs: sources (an array of objects, each with the same fields as format_citation: type, title and optional authors, year, container, publisher, city, edition, editors, translators, volume, issue, pages, doi, url, date_text, accessed, institution, degree, repository and report_number), dois (a list of DOIs to look up on Crossref), isbns (a list of ISBNs to look up on Open Library), urls (a list of web addresses to fetch and cite as websites) and style (apa7, mla9, chicago-ad, harvard, ieee, bibtex or ris). Give sources, dois, isbns, urls or any mix, up to 50 lookups in one call. If one lookup fails the reply is an error that names it. Example prompt: "Put these three sources into an APA works cited list: a journal article by Smith and Jones from 2020, a book by Cormen from 2009 and a website from example.edu."

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "format_bibliography"
  }
}

Input Schema

NameRequiredDescriptionDefault
doisNoDOIs to look up on Crossref and add to the list, each one a DOI like 10.1038/nature14539 or a doi.org link.
urlsNoWeb addresses to fetch and add to the list as websites. Each one a full URL like https://example.edu/study.
isbnsNoISBNs to look up on Open Library and add to the list as books. Dashes are fine.
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).apa7
sourcesNoThe sources for the list. Each one takes the same fields as format_citation, so a journal article, a book, a website, a chapter, a thesis, a report, a dataset and a preprint can share one list. Optional when you give dois, isbns or urls.

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."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)."
  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."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."
  3. Changed8 schema fields changedv0.1.6
    • addedInput schema / properties / dois
      Added value: +{
      +  "default": [],
      +  "description": "DOIs to look up on Crossref and add to the list, each one a DOI like 10.1038/nature14539 or a doi.org link.",
      +  "items": {
      +    "type": "string"
      +  },
      +  "type": "array"
      +}
    • addedInput schema / properties / isbns
      Added value: +{
      +  "default": [],
      +  "description": "ISBNs to look up on Open Library and add to the list as books. Dashes are fine.",
      +  "items": {
      +    "type": "string"
      +  },
      +  "type": "array"
      +}
    • addedInput schema / properties / sources / default
      Added value: +[]
    • changedInput schema / properties / sources / description
      Previous value: -"The sources for the list. Each one takes the same fields as format_citation, so a journal article, a book, a website, a chapter, a thesis, a report, a dataset and a preprint can share one list."New value: +"The sources for the list. Each one takes the same fields as format_citation, so a journal article, a book, a website, a chapter, a thesis, a report, a dataset and a preprint can share one list. Optional when you give dois, isbns or urls."
    • changedInput schema / properties / sources / items / properties / container / description
      Previous value: -"Journal name, the book title for a chapter, or website name."New value: +"Journal name, the book title for a chapter, or website name. Required for a journal article and for a chapter, since without it the citation would be missing the work it appears in."
    • 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."
    • addedInput schema / properties / urls
      Added value: +{
      +  "default": [],
      +  "description": "Web addresses to fetch and add to the list as websites. Each one a full URL like https://example.edu/study.",
      +  "items": {
      +    "type": "string"
      +  },
      +  "type": "array"
      +}
    • removedInput schema / required
      Removed value: -[
      -  "sources"
      -]
  4. First observedv0.1.3

TDQS

A4.2/5.0
Behavior5/5

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

Annotations already declare readOnlyHint and openWorldHint, and the description still adds real behavior: alphabetisation by first author's family name with a title fallback for anonymous works, IEEE numbered in citation order, BibTeX and RIS emitted in the order given, a 50-lookup ceiling, and all-or-nothing error handling that names the failing lookup. Those are exactly the details an agent cannot get from the annotations or schema.

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 purpose and ordering rules are front-loaded well, and the example prompt is a useful anchor. However, the long mid-sentence inventory of source fields (type, title, authors, year, container, publisher, city, edition, ...) duplicates the schema verbatim at 100% coverage and bloats an already dense single sentence.

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 tool this complex the description covers what matters: how the list is ordered per style, how inputs combine, the 50-lookup limit, and error behaviour. There is no output schema, and it only implicitly signals the return shape (a list, or one BibTeX/RIS block) rather than stating it, which is the one gap worth closing.

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 description coverage is 100%, so the schema already documents every parameter including the style enum values and the Crossref/Open Library lookups. The description largely re-enumerates the source object fields rather than adding meaning, though it does clarify that all four input arrays can be combined and that sources is optional when lookups are supplied. 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?

The description opens with a specific verb and resource — formatting several sources into one works cited list — and immediately pins down the scope that separates it from format_citation: many sources, one list, with per-style collation rules. It also distinguishes itself from the lookup siblings (cite_from_doi, cite_from_isbn, cite_from_url) by describing those as inputs it can absorb in bulk.

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?

Usage is clear: give sources, dois, isbns, urls or any mix, up to 50 lookups, and a failing lookup aborts with an error naming it. The example prompt shows a realistic invocation pattern. What is missing is explicit routing guidance — it never says to use format_citation for a single source or cite_from_doi when only one DOI is involved, leaving the agent to infer that from the 'same fields as format_citation' reference.

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