PaperMCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| OPENALEX_EMAIL | Yes | A valid email address for OpenAlex API access. OpenAlex requires an email for rate limiting and contact purposes. |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| paper_searchC | 智能学术论文检索系统，支持多维度相关性评分、学术质量评估、语义搜索等高级功能，专为研究员和教授设计 |
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 1 tool
With only one tool, there is no possibility of ambiguity or overlap with other tools. The tool's purpose is clearly defined as an intelligent academic paper search system, making it impossible for an agent to misselect between non-existent alternatives.
The single tool name 'paper_search' follows a clear verb_noun pattern (search as the verb, paper as the noun). Since there are no other tools to compare against, consistency is inherently perfect with no deviations or mixed conventions.
A single tool is generally too few for most server purposes, as it limits functionality and may indicate an incomplete or overly narrow scope. While the tool is described as advanced, a server focused on academic paper retrieval would typically benefit from additional tools (e.g., for filtering, citation analysis, or paper details) to provide comprehensive coverage.
The server's domain appears to be academic paper retrieval, but with only a search tool, there are significant gaps. For example, there are no tools for accessing paper metadata, downloading papers, managing searches, or handling citations, which are common needs in this domain. This incomplete surface will likely cause agent failures when trying to perform full research workflows.