paper-download-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 |
|---|---|
| paper_download_healthA | Report version, staging dir, provider availability. Never prints API keys or credentials. |
| paper_download_list_providersA | List available download providers and their status. |
| paper_download_probeB | Probe whether a provider can likely fetch the given identifier. Args: identifier: DOI (e.g. 10.1016/j.x) or UT. provider_hint: If given, only this provider is considered. |
| paper_download_fetchA | Fetch a paper into the staging area; return artifact metadata. Does NOT accept project, output_dir, year, publisher, or final filename. The caller moves the verified artifact to final storage. Args: identifier: DOI or UT. provider_hint: Preferred provider name (hard constraint if given). |
| paper_download_verify_artifactA | Verify a staged artifact: existence, PDF validity, page count, hash. |
| paper_download_discard_artifactC | Remove a staged artifact from the staging area. |
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 6 tools
Each tool has a clear, distinct role in the fetch→verify→discard workflow, plus provider/system introspection. Fetch and probe are differentiated by actual download vs. likelihood check, and health versus list_providers is similarly distinct.
All tools share the paper_download_ prefix and use snake_case, but most follow a verb_noun pattern while paper_download_health uses a noun. The overall convention is still predictable and readable.
With six tools covering fetch, discard, probe, health, provider listing, and verification, the count is well-scoped for a focused paper-download staging service. Each tool earns its place and there is no bloat.
The core lifecycle of fetching, verifying, discarding, and probing is covered, and provider/health introspection is present. A minor gap is the lack of a tool to list currently staged artifacts, though the workflow is still usable without it.