Skip to main content
Glama

Quill Scholar Research Desk

Literature review pack

literature_review
Read-only

Literature review pack for a research topic: a staged reading list (foundation / core / frontier) with summaries, citation counts and links, the most-cited foundations, the recent frontier, papers per year, top venues, prolific authors, key terms, a short synthesis that cites only the listed papers (themes, open questions, where to start), next queries and a BibTeX file. Sources: arXiv, Crossref, DBLP, Europe PMC, OpenAlex. Needs a Quill Research Pass (1 USDC = 24 h, 5 USDC = 7 days, 15 USDC = 30 days by plain USDC transfer on Base; see payment_options), or pay per call over HTTP x402 ($0.25) at /v1/review.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "topic": "<topic>"
    },
    "name": "literature_review"
  }
}

Input Schema

NameRequiredDescriptionDefault
nNoReading list length, 5-30 (default 15).
passNoOptional Quill Research Pass token (qp1...). Better: set it once as the MCP header Authorization: Bearer <token>.
fieldNoauto (default) searches all indexes; cs = arXiv+DBLP+Crossref; bio = Europe PMC+Crossref; general = all except DBLP.
sinceNoOnly papers published in or after this year (optional).
topicYesResearch topic, 1-10 content words (e.g. "graph neural networks drug discovery"). Omit for a demo.
synthesisNoInclude the written synthesis (default 1).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior5/5

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

Beyond the readOnly and openWorld annotations, the description discloses the full output shape, the data sources used, and important access requirements. It explains that a Quill Research Pass or x402 per-call payment is needed, including pass durations and pricing.

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

Conciseness4/5

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

The description is front-loaded with the core purpose and then lists outputs and access details efficiently. It is dense and runs as one long sentence, but most of the detail is useful for setting expectations on a complex tool.

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?

There is no output schema, so the description must explain return values, and it does so thoroughly by listing the staged reading list, summaries, citation counts, venue and author stats, synthesis, next queries, and BibTeX. It also covers payment and source behavior, making the definition complete for this complexity.

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

Parameters3/5

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

Schema description coverage is 100%, so all six parameters are already documented in the input schema. The description adds context about the overall pack but does not meaningfully elaborate on n, field, since, synthesis, or the pass parameter beyond what the schema states.

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?

The description states a specific resource, a literature review pack, and enumerates its distinctive outputs: staged reading list, citation counts, synthesis, next queries, and BibTeX. This clearly separates it from a simple paper search or citation lookup.

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

Usage Guidelines3/5

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

The description implies the tool is for generating a structured literature review on a topic, but it does not explicitly say when to use it versus siblings like search_papers or cite. It also does not name alternatives or exclusions.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources