Skip to main content
Glama

Cite from an ISBN

cite_from_isbn
Read-only

Look up an ISBN on Open Library and format the book citation in APA 7, MLA 9, Chicago author-date, Harvard, IEEE, BibTeX, or RIS.

Instructions

Look up an ISBN on Open Library and format the book citation in APA 7, MLA 9, Chicago author date, Harvard, IEEE or BibTeX. Inputs: isbn (a 10 or 13 digit ISBN, dashes are fine) 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 ISBN 978-0-262-03384-8 in MLA 9."

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": {
      "isbn": "<isbn>"
    },
    "name": "cite_from_isbn"
  }
}

Input Schema

NameRequiredDescriptionDefault
isbnYesA 10 or 13 digit ISBN. 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), 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."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."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. 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."
  4. First observedv0.1.3

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, and the description usefully names Open Library as the external source and describes the reply shape (style name on the line above each citation). It adds no error behavior for an invalid or unknown ISBN, no rate-limit or latency note for the external lookup, and its "all three styles" claim is internally inconsistent with the six styles it lists.

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?

Front-loaded with purpose then inputs then output conventions; every sentence is functional and the example prompt is a cheap way to show a real invocation. Minor deduction because "all three styles" is a misleading compression of the six style choices enumerated one clause earlier.

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 supplies the missing return-format detail (each citation labeled with its style name, bibtex yielding a single .bib entry), which is exactly what an agent needs. It stops short of covering failure modes for a bad ISBN or divergence between the style list here and the schema's ris option.

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 both params, including the ris alias. The description restates the dash tolerance and style values almost verbatim and even omits the ris option the schema offers, so it adds little meaning beyond structured fields.

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 ("Look up an ISBN on Open Library") plus the resource and the transform applied (format book citation in APA 7, MLA 9, Chicago author date, Harvard, IEEE or BibTeX). The ISBN input alone distinguishes it from cite_from_doi, cite_from_url and cite_from_arxiv without opening any schema.

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?

Gives in-tool guidance for parameter choices ("Pass all to get all three styles", "Pass bibtex to get one .bib entry for a reference manager") and an example prompt. It never says when to pick this over the sibling citers (DOI/URL/arXiv) or what happens if the ISBN is unknown, so routing across the family is left to inference.

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