Skip to main content
Glama
Sign In
NASA ADS MCP Server

NASA ADS MCP Server

by prtc
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Export BibTeX

export_bibtex
Read-onlyIdempotent

Exports BibTeX citations in ADS format for bibcodes, DOIs, or arXiv IDs, ready to paste into LaTeX or Quarto documents, and flags any bibcodes that changed.

Instructions

Export BibTeX citations for one or more papers, exactly as ADS formats them (journal macros, volume, pages, DOI, eprint). Accepts bibcodes, DOIs and arXiv IDs; the BibTeX key is always ADS's current bibcode, and the result notes any that changed. Useful for adding references to LaTeX/Quarto documents.

Input Schema

NameRequiredDescriptionDefault
bibcodesYesBibcodes (e.g. '2005A&A...443..735C'), DOIs or arXiv IDs (e.g. 'arXiv:1404.3243'). Earlier bibcodes (arXiv preprint, MNRAS '.tmp.') also work.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.8.0
    • changedInput schema / properties / bibcodes / description
      Previous value: -"List of ADS bibcodes to export"New value: +"Bibcodes (e.g. '2005A&A...443..735C'), DOIs or arXiv IDs (e.g. 'arXiv:1404.3243'). Earlier bibcodes (arXiv preprint, MNRAS '.tmp.') also work."
    • addedInput schema / properties / bibcodes / title
      Added value: +"Bibcodes"
    • addedInput schema / title
      Added value: +"export_bibtexArguments"
  2. Changed1 schema field changedv0.4.1
    • addedInput schema / properties / bibcodes / minItems
      Added value: +1
  3. First observedv1.0.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly/openWorld/idempotent/non-destructive, so safety is covered. The description adds real behavioral detail beyond that: the BibTeX key is always ADS's current bibcode and the response flags any bibcodes that changed — non-obvious behavior an agent would otherwise not know.

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?

Two sentences, front-loaded with purpose and format guarantee, then identifier handling, then the use case. There is no filler or repetition across clauses.

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?

With no output schema, the description still covers what matters: it names the fields emitted (journal macros, volume, pages, DOI, eprint) and notes that changed bibcodes are reported. For a one-parameter read-only export tool this is sufficient to call correctly.

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% and the single parameter already documents bibcodes, DOIs, arXiv IDs, and legacy bibcodes. The description restates the accepted identifier types but adds no syntax or format detail beyond the schema, so the 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?

States a specific verb and resource ('Export BibTeX citations') plus the exact format guarantee ('exactly as ADS formats them'), and the parenthetical enumerates which fields are included. It is clearly distinguishable from siblings like get_paper_details, which retrieve metadata rather than a formatted citation.

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?

Provides a concrete use case ('adding references to LaTeX/Quarto documents') that tells the agent when this tool is the right choice, but stops short of naming an alternative or a when-not condition. Clear context, no exclusions.

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

Deploy Server

Other Tools