Skip to main content
Glama
Liyux3

scholar-mcp

by Liyux3

search_papers

Search academic papers across Semantic Scholar, arXiv, and OpenAlex with LLM-powered reranking for relevant results.

Instructions

Search for academic papers across multiple sources (Semantic Scholar, arXiv, OpenAlex). Results are ranked using LLM-based reranking for better relevance.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesSearch query (e.g., "attention is all you need", "CRISPR gene editing")
limitNoMaximum results to return (1-100, default 10)
yearNoFilter by year or range (e.g., "2023", "2020-2024")
venueNoFilter by venue (e.g., "NeurIPS", "Nature")
fields_of_studyNoComma-separated fields (e.g., "Computer Science,Mathematics")
paper_typesNoComma-separated types (e.g., "JournalArticle,Conference,Review,Book,Dataset"). Default: all types.
min_citationsNoMinimum citation count filter (default 0)
open_access_onlyNoOnly return papers with free PDF access
sortNoSort results by "citations" (most cited first) or "date" (newest first). Default: relevance.
intentNoRanking preference. "foundational" for seminal papers, "recent" for latest work, "survey" for reviews, "method" for specific techniques. Default: balanced relevance.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior2/5

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

No annotations are provided, so the description must fully disclose behavioral traits. It mentions multi-source search and reranking but does not discuss rate limits, authentication requirements, result caching, or potential delays. This is insufficient for a tool with no annotations.

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 just two sentences, with the first focusing on purpose and the second on a key advantage (LLM reranking). Every word adds value; there is no redundancy or 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 10 parameters, 100% schema coverage, and the existence of an output schema, the description covers the core functionality well. However, it lacks usage context and behavioral details, preventing a perfect score.

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%, so the schema already documents all 10 parameters thoroughly. The description adds no parameter-specific information beyond the schema, meeting the baseline of 3.

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 it searches academic papers across multiple named sources (Semantic Scholar, arXiv, OpenAlex) and uses LLM-based reranking. This distinguishes it from sibling tools like search_authors (which searches authors) and recommend_papers (which recommends papers).

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 description does not explicitly state when to use this tool vs alternatives. It implies usage for cross-source paper searching but lacks instructions on when not to use it or when to prefer siblings like recommend_papers or discover_field.

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

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