Skip to main content
Glama
YGao2005

Scholar Feed MCP Server

Get Citations

get_citations
Read-only

Sort papers in a citation graph by impact score. Fetch either outgoing references or incoming citations for a given arXiv ID.

Instructions

Get the citation graph for a paper, sorted by citing-paper rank_score (highest-impact first). 'citing' = outgoing references this paper cites; 'cited_by' = incoming citations from other papers. Default response is a lean 12-field shape per paper — pass verbose=true for the full 28-field shape.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
arxiv_idYesarXiv ID of the paper
directionNo'citing' = outgoing references this paper cites; 'cited_by' = incoming citations from other paperscited_by
limitNoNumber of papers to return (max 50)
fieldsNoComma-separated list of fields to return (e.g. 'arxiv_id,title,llm_summary,llm_novelty_score'). If omitted, returns the lean 12-field default unless verbose=true.
verboseNoIf true, returns the full 28-field paper shape. Default false returns the lean 12-field set. Ignored when `fields` is provided.
exclude_idsNoarXiv IDs to exclude from results (for deduplication across chained calls)

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
Behavior5/5

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

Annotations already indicate readOnlyHint=true and destructiveHint=false. The description adds valuable behavioral details: sorting by citing-paper rank_score, default response shape (lean 12-field vs full 28-field with verbose), and the interaction between fields and verbose. No contradictions.

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?

The description is three sentences, each with distinct purpose: main action, direction explanation, response shape details. Front-loaded with the primary purpose, no fluff.

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?

Given the complexity (citation graph, directions, sorting, response shape options) and the presence of an output schema covering return values, the description provides sufficient context. It could mention rank_score's meaning, but overall it's complete enough.

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

Parameters4/5

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

Schema coverage is 100% with descriptions for all parameters. The description adds semantic value beyond the schema by specifying the sorting order (by rank_score), clarifying the direction enum values, and explaining the verbose/fields default 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 retrieves the citation graph for a paper, and distinguishes between 'citing' and 'cited_by' directions. It uses a specific verb ('get') and resource ('citation graph'), and implicitly differentiates from sibling tools like search_papers or co_author_graph.

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?

The description explains when to use each direction ('citing' = references, 'cited_by' = citations) and how to get more fields (verbose=true). It does not explicitly mention when not to use this tool or alternatives, but the context is clear enough for typical use.

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