semantic-scholar-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_papersA | 搜索学术论文 :param query: 搜索查询字符串 :param limit: 返回结果数量(默认5，最大100) |
| download_paperA | 根据DOI下载论文PDF :param doi: 论文的DOI标识符 :param output_dir: PDF输出目录（可选） :return: 下载结果信息 |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 2 tools
The two tools have completely distinct purposes: one searches for academic papers, the other downloads a PDF by DOI. There is no overlap or ambiguity between them.
Both tool names follow the verb_noun pattern (search_papers, download_paper), which is consistent, predictable, and easy to understand.
With only 2 tools, the server feels significantly under-scoped for a service like Semantic Scholar. A typical integration would include many more capabilities, such as retrieving paper metadata, authors, citations, and recommendations, making this count too low for the domain.
The tool surface covers only search and PDF download by DOI. Major functionalities like fetching paper details by ID, exploring citations/references, and author information are missing, leaving obvious gaps that could cause agent failures.