classScopusMCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SCOPUS_API_KEY | Yes | Your Scopus API key. Obtain from Elsevier Developer Portal. |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_papersA | 키워드로 논문을 검색하고 초록을 가져옵니다. |
| get_abstract_by_doiB | DOI로 특정 논문의 초록을 가져옵니다. |
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 are clearly distinct: one searches by keyword, the other retrieves a specific paper by DOI. There is no ambiguity in purpose, as each targets a different lookup method.
Both tool names follow a consistent verb_noun pattern with snake_case: 'search_papers' and 'get_abstract_by_doi'. The naming is predictable and descriptive.
While only two tools are provided, they are well-scoped for the stated purpose of searching papers and fetching abstracts by DOI. The count is slightly lean but not unreasonable for a focused utility.
The tool set covers the essential operations for finding papers and obtaining abstracts. Minor gaps exist, such as lack of citation data or full metadata retrieval, but the core workflow is complete.