Skip to main content
Glama

arxiv_search

Search arXiv preprints by keywords, field syntax, or ID to retrieve titles, authors, abstracts, categories, DOIs, and PDF links for research discovery.

Instructions

arXiv preprint search (plain words or arXiv field syntax ti:, au:, abs:, cat:) or id lookup: title, authors, dates, categories, abstract, DOI, journal ref, abs and PDF links. Costs 0.002 USDC on Base per successful call (x402). Without a payment key this tool returns the 402 challenge.

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_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
qNoQuery
idNoarXiv id(s), comma-separated
maxNo1-25, default 5
sortNorelevance, submitted, updated

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.0

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does real work: it discloses the x402 payment model, the 0.002 USDC cost on Base per successful call, and the exact failure behavior when no payment key is present. It omits pagination/result-window behavior beyond the max parameter and gives no sense of failure modes other than the 402.

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?

Three sentences, front-loaded with the capability and the query-syntax vocabulary before the cost caveat, which is the right ordering for an agent deciding whether to call. The first sentence is a dense run-on listing output fields, which slightly hurts readability but nothing is wasted.

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?

For a four-parameter search tool with no output schema and no annotations, the description covers the query language, the id path, the returned fields, and the payment gate. An agent can decide and invoke correctly without opening the schema.

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

Parameters4/5

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

Schema description coverage is 100%, so the baseline is 3; the description exceeds it by explaining the arXiv field syntax (ti:, au:, abs:, cat:), the comma-separated id form, and enumerating the returned metadata. It does not add format detail for q when using field syntax combinations or clarify the string-typed numeric params.

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?

The description names a specific verb+resource ('arXiv preprint search') and covers both modes (keyword query with arXiv field syntax, or id lookup), plus the fields returned. It does not differentiate itself from the sibling pubmed_search, which is a plausible confusion point for a literature-search agent, so it stops short of a 5.

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?

It states the two calling modes (plain words / arXiv field syntax vs. id lookup) and gives a hard precondition: without a payment key the call returns the 402 challenge. That is clear context for when the tool is usable, but there is no explicit guidance on choosing between full-text search and id lookup or between this and other literature sources.

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