Skip to main content
Glama
Sign In
NASA ADS MCP Server

NASA ADS MCP Server

by prtc
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Get paper details

get_paper_details
Read-onlyIdempotent

Retrieve abstracts, authors, publication details, DOIs, arXiv IDs, keywords, and citations for up to 20 papers via bibcodes, DOIs, or arXiv IDs; flags records missing from ADS.

Instructions

Get full details for up to 20 papers in one call: abstract, authors, publication (journal, volume, page), DOI, arXiv ID, keywords and citations. Accepts bibcodes, DOIs and arXiv IDs, and says which ones ADS doesn't have.

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. Changed4 schema fields changedv0.8.0
    • removedInput schema / properties / bibcode
      Removed value: -{
-  "description": "ADS bibcode (e.g., '2019ApJ...878...98S')",
-  "type": "string"
-}
    • addedInput schema / properties / bibcodes
      Added value: +{
+  "description": "Bibcodes (e.g. '2005A&A...443..735C'), DOIs or arXiv IDs (e.g. 'arXiv:1404.3243'). Earlier bibcodes (arXiv preprint, MNRAS '.tmp.') also work.",
+  "items": {
+    "type": "string"
+  },
+  "maxItems": 20,
+  "minItems": 1,
+  "title": "Bibcodes",
+  "type": "array"
+}
    • changedInput schema / required
      Previous value: -[
-  "bibcode"
-]New value: +[
+  "bibcodes"
+]
    • addedInput schema / title
      Added value: +"get_paper_detailsArguments"
  2. First observedv1.0.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds genuinely new behavioral context: the 20-item batch cap and, importantly, that the response reports which requested identifiers ADS doesn't have, which tells the agent how partial results are surfaced.

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?

A single dense sentence front-loads the capability and batch limit, then lists returned fields and accepted identifier types. No filler, no repetition.

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 return-value burden and does so by enumerating the main fields. It is nearly complete for a single-parameter read tool; only edge behavior (e.g. what happens to invalid identifiers vs. simply-absent ones) is unspecified.

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%, and the schema already documents that the bibcodes array accepts DOIs, arXiv IDs and legacy bibcode forms plus the maxItems of 20. The description restates rather than extends that, adding no format or normalization detail beyond the schema. Baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ("Get full details for up to 20 papers") and enumerates the returned fields (abstract, authors, publication, DOI, arXiv ID, keywords, citations), which clearly separates it from search_papers. It never names a sibling tool explicitly, so the differentiation is implicit rather than stated.

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?

The batched nature ("up to 20 papers in one call") implies you should prefer this over repeated single lookups, but there is no explicit when-to-use or when-not-to-use guidance. Nothing tells the agent when search_papers or get_paper_metrics is the better entry point.

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