literature-bot-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DASHSCOPE_MODEL | Yes | The model ID provided by the service provider. | |
| DASHSCOPE_API_KEY | Yes | Your API key for the model service. | |
| DASHSCOPE_BASE_URL | Yes | The base URL of the model service, e.g., https://your-service-url/v1. Do not append /chat/completions. |
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 |
|---|---|
| literature_search_papersA | Search arXiv and return concise paper metadata. Use this first when the user wants literature recommendations or has not supplied an arXiv ID. It does not download PDFs. The returned arXiv IDs can be passed to the other literature tools. |
| literature_get_paper_detailsA | Return detailed metadata for one arXiv paper. Use this for title, authors, abstract, categories, dates, and URLs. If the paper has not been seen in this session, the server resolves the ID through arXiv. It does not download the PDF. |
| literature_prepare_paperA | Download, extract, and chunk one paper for evidence retrieval. The PDF is cached in the configured local papers directory and is not overwritten. Extracted pages and chunks stay only in server memory. Repeating the call is safe and reuses the cache. |
| literature_retrieve_paper_evidenceA | Retrieve page-cited evidence chunks from one paper. Use this before answering a question about paper content. The query must be concise English keywords because retrieval uses local BM25 rather than a model. If necessary, the paper is prepared automatically. Return the page numbers with any answer built from these results. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| search_literature | Search arXiv for a topic and present a concise list of relevant papers. |
| analyze_paper | Answer a specific question about one paper using retrieved, page-cited evidence. |
| summarize_paper | Summarize one paper's problem, methods, experiments, and conclusions with page citations. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| literature_guide | Workflow and citation guidance for this literature server. |
TDQS
Scored across 4 tools
Each tool targets a distinct stage: search, metadata details, preparation/download, and evidence retrieval. The only mild overlap is prepare_paper vs retrieve_paper_evidence, since retrieve auto-prepares when needed, but descriptions clarify the distinction well.
All four tools follow a strict literature_verb_noun pattern (search_papers, get_paper_details, prepare_paper, retrieve_paper_evidence), making the namespace and conventions fully predictable.
Four tools is slightly lean but well-matched to a focused paper search-and-retrieval server. Each tool earns its place with a distinct role in the pipeline.
The surface covers a coherent lifecycle: search, inspect metadata, prepare, and retrieve cited evidence. Minor gaps exist (no listing/clearing of the local cache), but core literature workflows are fully supported.