Skip to main content
Glama

Quill Scholar Research Desk

Latest arXiv papers

arxiv_latest
Read-only

The newest arXiv submissions in any category (cs.AI, cs.CL, q-bio.GN, stat.ML, ...), optionally filtered by keywords: titles, authors, summaries, links, papers per day and trending terms. 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.02) at /v1/arxiv/latest.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "arxiv_latest"
  }
}

Input Schema

NameRequiredDescriptionDefault
nNoNumber of papers, 5-50 (default 25).
qNoOptional keywords that must appear in title or abstract (e.g. "agents tool use").
catNoarXiv category, e.g. cs.AI, cs.CL, cs.LG, cs.CV, stat.ML, q-bio.GN, quant-ph (default cs.AI).
passNoOptional Quill Research Pass token (qp1...). Better: set it once as the MCP header Authorization: Bearer <token>.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover read-only and open-world behavior, and the description adds genuinely useful context beyond them: the Quill Research Pass tiers (1/5/15 USDC for 24h/7d/30d), the x402 per-call price of $0.02, and the endpoint. It does not define the freshness window of "latest", pagination, or rate/error behavior, which keeps it short of a 5.

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?

Purpose and scope are front-loaded in the first sentence, with commercial/authentication details following. The second sentence is dense with pricing minutiae, but that information is useful rather than filler, and there is no redundant restatement of the title.

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

Completeness4/5

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

For a four-parameter, no-output-schema tool, the definition covers what the tool returns at a high level, the default category and count behavior via the schema, and the two authentication/cost paths. Missing only a definition of the recency window and response shape, which is a minor gap given there is no output schema.

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 the schema already documents n, q, cat, and pass including ranges and defaults. The description adds the category examples and roughly restates keyword filtering semantics, but contributes little meaning beyond the schema; baseline 3 applies.

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

Purpose4/5

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

States a specific verb and resource ("newest arXiv submissions") plus an explicit scope (any category) and optional keyword filtering, which distinguishes it from a general paper search. However, the colon list ("titles, authors, summaries, links, papers per day and trending terms") reads as return fields grafted onto a sentence about keyword filtering, leaving mild ambiguity about what is actually filterable.

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?

Usage context is implied by "newest" versus the sibling search_papers, and the payment paths are spelled out, but there is no explicit statement of when to choose this over search_papers or literature_review. The agent must infer the recency-oriented use case.

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