Skip to main content
Glama
prtc
by prtc

get_paper_details

Retrieve comprehensive metadata for astronomical papers from NASA ADS using bibcodes, including abstracts, authors, citations, and keywords.

Instructions

Get detailed information about a specific paper using its bibcode. Returns full metadata including abstract, authors, citations, keywords, and more.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bibcodeYesADS bibcode (e.g., '2019ApJ...878...98S')

Implementation Reference

  • The handler function that implements the core logic for retrieving detailed paper information using the ADS API, formatting title, authors, abstract, keywords, etc.
    async def get_paper_details(bibcode: str) -> list[TextContent]:
        """Get detailed information about a specific paper."""
        try:
            papers = list(ads.SearchQuery(
                bibcode=bibcode,
                fl=["bibcode", "title", "author", "year", "citation_count", 
                    "abstract", "keyword", "doi", "pubdate", "pub"],
            ))
            
            if not papers:
                return [TextContent(
                    type="text",
                    text=f"Paper not found: {bibcode}"
                )]
            
            paper = papers[0]
            
            # Format authors
            authors = paper.author if paper.author else ["Unknown"]
            author_str = "; ".join(authors)
            
            # Format keywords
            keywords = ", ".join(paper.keyword) if paper.keyword else "None"
            
            # Build detailed response
            details = [
                f"Title: {paper.title[0] if paper.title else 'No title'}",
                f"Authors: {author_str}",
                f"Publication: {paper.pub or 'Unknown'}",
                f"Year: {paper.year}",
                f"Citations: {paper.citation_count or 0}",
                f"DOI: {paper.doi[0] if paper.doi else 'N/A'}",
                f"Keywords: {keywords}",
                f"Bibcode: {paper.bibcode}",
                "",
                "Abstract:",
                paper.abstract or "No abstract available",
            ]
            
            return [TextContent(type="text", text="\n".join(details))]
        
        except Exception as e:
            logger.error(f"Error getting paper details: {e}")
            return [TextContent(
                type="text",
                text=f"Error getting paper details: {str(e)}"
            )]
  • The tool registration in list_tools(), defining the tool name, description, and input schema.
    Tool(
        name="get_paper_details",
        description=(
            "Get detailed information about a specific paper using its bibcode. "
            "Returns full metadata including abstract, authors, citations, keywords, and more."
        ),
        inputSchema={
            "type": "object",
            "properties": {
                "bibcode": {
                    "type": "string",
                    "description": "ADS bibcode (e.g., '2019ApJ...878...98S')",
                },
            },
            "required": ["bibcode"],
        },
    ),
  • Input schema defining the required 'bibcode' parameter as a string.
    inputSchema={
        "type": "object",
        "properties": {
            "bibcode": {
                "type": "string",
                "description": "ADS bibcode (e.g., '2019ApJ...878...98S')",
            },
        },
        "required": ["bibcode"],
    },
  • Dispatch logic in the main call_tool handler that routes to the get_paper_details function.
    elif name == "get_paper_details":
        return await get_paper_details(bibcode=arguments["bibcode"])
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions the tool 'Returns full metadata including abstract, authors, citations, keywords, and more,' which gives some output context, but lacks details on error handling, rate limits, authentication needs, or data freshness. For a read operation without annotations, this is a significant gap in transparency.

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?

The description is concise and front-loaded, stating the core purpose in the first sentence. The second sentence elaborates on return values efficiently. There's no wasted text, though it could be slightly more structured for clarity. It earns its place but isn't perfectly optimized.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's low complexity (1 parameter, no nested objects) and high schema coverage, the description is adequate but incomplete. It lacks an output schema, so the description partially compensates by listing return metadata. However, without annotations and with sibling tools present, more context on usage and behavior would improve completeness for an AI agent.

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?

The input schema has 100% description coverage, with the 'bibcode' parameter well-documented in the schema itself. The description adds minimal value beyond the schema by implying the bibcode is used to fetch paper details, but doesn't provide additional syntax, format nuances, or examples. This meets the baseline of 3 when schema coverage is high.

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?

The description clearly states the tool's purpose: 'Get detailed information about a specific paper using its bibcode.' It specifies the verb ('Get'), resource ('paper'), and identifier ('bibcode'), making the action clear. However, it doesn't explicitly differentiate from sibling tools like 'get_paper_metrics' or 'get_author_papers', which prevents a score of 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives. It mentions retrieving 'detailed information' but doesn't clarify if this is for metadata vs. metrics or how it differs from tools like 'get_paper_metrics' or 'search_papers'. No exclusions or prerequisites are stated, leaving usage ambiguous.

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

Install Server

Other Tools

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/prtc/nasa-ads-mcp'

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