Skip to main content
Glama
YGao2005

Scholar Feed MCP Server

Get Paper

get_paper
Read-only

Retrieve paper details, summaries, and citation entries by providing one or more arXiv IDs. Supports batch lookup of up to 50 papers and BibTeX export.

Instructions

Get full details for one or more papers by arXiv ID. Pass a single-element array for one paper; pass multiple IDs to batch-fetch up to 50 papers in one call (replaces the removed batch_lookup tool). Pass format='bibtex' to get a .bib citation entry (replaces the removed export_bibtex tool — bibtex is single-paper only; for multi-paper bibtex, call repeatedly). Default returns a lean 14-field shape (arxiv_id, title, authors, year, categories, has_code, github_url, citation_count, venue_name, llm_summary, llm_significance, llm_novelty_score, impact_pct, impact_tier — where impact_pct is the ML-forecast per-category impact percentile 0-100 and impact_tier its A+/A/B/C/D grade; both NULL on older papers outside the recent scoring window). Pass verbose=true for the full shape with structured extraction (method_name, contribution_type, task_category, datasets, baselines) and institution_tags. Use fields='arxiv_id,title,abstract' to select an exact subset, or fetch_fulltext with sections='all' for the full paper.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
arxiv_idsYesOne or more arXiv IDs. Single-paper lookup uses [id]; batch lookup passes multiple IDs (max 50). Replaces the removed batch_lookup tool. Example: ['2407.15831'] or ['2407.15831', '2402.09906'].
formatNoResponse format. 'json' (default) returns structured paper data. 'bibtex' returns a .bib citation entry — replaces the removed export_bibtex tool. Bibtex mode uses the first ID in arxiv_ids.
fieldsNoComma-separated list of fields to return (e.g. 'arxiv_id,title,llm_summary,abstract'). If omitted, returns the lean 12-field default unless verbose=true.
verboseNoIf true, returns the full 28-field paper shape (method/task/dataset extraction, application_domain, baselines, etc.). Default false returns the lean 12-field set. Ignored when `fields` is provided.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
papersNoMatched / returned papers.
totalNoTotal results available for the query.
pageNo
limitNo
modeNoSearch mode actually applied.
directionNoCitation direction (get_citations: citing | cited_by).
topicNo
noteNo
not_foundNoRequested IDs that had no match.
next_cursorNoKeyset cursor for the next page, or null when exhausted.
hitsNoNew watch matches (check_watches).
resultsNo
bibtexNoBibTeX entry (format='bibtex').
countNo
formatNo
okNo
messageNo
Behavior5/5

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

Annotations indicate read-only safety; description adds batch limits, NULL handling for older papers, behavior of verbose and fields parameters, and bibtex mode restrictions.

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?

While well-structured and informative, the description is verbose, repeating replacement tool mentions and listing many fields inline. Could be tighter.

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?

Covers all aspects: batch limits, format options, default/verbose shapes, field selection, edge cases (NULL for older papers), and relationship to siblings.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, but description adds significant meaning: default vs verbose shapes, specific field names, impact score interpretation, and bibtex behavior.

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 clearly states the tool gets full details for papers by arXiv ID, distinguishes from siblings like fetch_fulltext and search_papers, and explains replacement of removed tools.

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

Usage Guidelines5/5

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

Explicit guidance on single vs batch, bibtex mode, verbose vs default, and field selection. Notes bibtex is single-paper only and suggests fetch_fulltext for full text.

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/YGao2005/scholar-feed-mcp'

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