Skip to main content
Glama
retospect

acatome-quest-mcp

by retospect

submit

Submit a paper request to resolve metadata, check duplicates, and queue for fetch. Accepts DOI, arXiv, or free-form citations.

Instructions

Submit a paper request. Resolves metadata, checks dedup, queues for fetch.

Args: ref: The paper identifier. Any subset of: {doi, arxiv, pmid, title, authors, year, raw}. raw is a free-form citation string — Quest will try to extract a DOI or arXiv id from it. dry_run: If True, resolve and return candidates but do not persist. source: Provenance — e.g. {"document": "ch02.tex", "line": 147}. priority: Higher = served first by the runner. Default 0. created_by: Agent slug or user id. Used for per-agent rate-limiting.

Returns: The full request record, including resolved metadata, candidates, and misconceptions. Status will be one of: found_in_store (already have it), queued (waiting for runner), needs_user (disambiguation or bad DOI required manual action).

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 ingested or found_in_store.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
refYes
dry_runNo
sourceNo
priorityNo
created_byNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, description fully discloses behavior: resolution, dedup, queuing, idempotency, statuses, and per-agent rate-limiting. No contradictions.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Well-structured with Args and Returns sections. Concise yet comprehensive; every sentence provides value. Front-loaded with purpose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Covers all parameters and return values, including idempotency and statuses. Output schema exists but description still adds context. Complete for tool complexity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Despite 0% schema coverage, description thoroughly explains each parameter: ref (subsets, raw), dry_run, source, priority, created_by. Adds significant meaning beyond bare schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Clearly states 'Submit a paper request' and explains the process (resolves metadata, checks dedup, queues). Distinguishes from siblings like submit_file by focusing on reference-based submission.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides implicit guidelines through dry_run parameter for testing and priority/created_by for rate-limiting. Also warns not to fabricate quotes from non-ingested papers. Lacks explicit comparison to siblings but still informative.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/retospect/acatome-quest-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server