acatome-quest-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DATABASE_URL | No | Postgres DSN | postgresql://localhost/cluster |
| QUEST_SCHEMA | No | Schema name for the requests table | papers |
| ACATOME_INBOX | No | Drop directory watched by acatome-extract | ~/.acatome/inbox |
| UNPAYWALL_EMAIL | Yes | Polite-pool contact (required at runner start) | |
| QUEST_POLL_INTERVAL | No | Runner tick seconds | 30 |
| QUEST_INGEST_TIMEOUT | No | Seconds to wait for ingest after PDF drop | 900 |
| QUEST_MAX_CONCURRENT | No | Max parallel fetches | 4 |
| ACATOME_CROSSREF_MAILTO | No | Crossref polite pool (recommended) | |
| QUEST_MAX_OPEN_PER_AGENT | No | Per-created_by cap | 50 |
| SEMANTIC_SCHOLAR_API_KEY | No | Raises S2 rate limit (optional) |
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 |
|---|---|
| submitA | Submit a paper request. Resolves metadata, checks dedup, queues for fetch. Args:
ref: The paper identifier. Any subset of:
Returns:
The full request record, including resolved metadata, candidates, and
misconceptions. Status will be one of:
Idempotent: calling submit twice with the same DOI while the first request is still open returns the same request id. Do not fabricate quotes from a paper whose status is not |
| statusA | Read one or many paper requests. Args:
id: A request id (uuid string). If given, Returns:
A single card (when |
| updateA | Mutate a request. Single verb with an explicit Modes:
confirm: pick one of |
| submit_fileA | Attach a user-supplied PDF to a paper request. Use this when a user drops a PDF (e.g. a Discord attachment) for a paper that Quest could not fetch automatically, or to pre-load a PDF you already have on disk. Args:
url: A direct HTTP(S) link to the PDF. Must resolve to a fresh file
(follow-redirects is enabled, so short-lived Discord CDN URLs
work). Mutually exclusive with Returns:
The full request record, flipped to Exactly one of |
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 4 tools
Each tool has a clearly distinct purpose: status for reading, submit for creating, submit_file for attaching PDFs, and update for modifying requests. No overlap exists, and descriptions are detailed enough to prevent confusion.
Names are lowercase and follow a simple pattern: three verbs (status, submit, update) and one compound verb_noun (submit_file). While not perfectly uniform, the naming is clear and predictable with minor deviations.
With 4 tools covering the core operations (create, read, update, attach file), the count is appropriate for the server's focused scope. It is slightly on the lower side but not insufficient.
The tool set covers the main lifecycle of paper requests: submission, status query, file attachment, and various update modes (including cancel). A minor gap is the lack of an explicit delete tool, but cancel effectively serves that purpose.