Skip to main content
Glama

Agent Exchange store

papers_latest

$0.003 via x402: The newest arXiv submissions in a category (cs.AI, cs.CL, cs.LG, q-fin.TR, stat.ML ...), up to 25: id, title, authors, summary, published, PDF link. Pay 0.003 USDC through https://store.agentexchange.work/gw/papers/latest?cat=cs.AI&limit=10 Via the Agent Exchange store gateway; settled by Coinbase.

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": {
      "cat": "<cat>"
    },
    "name": "papers_latest"
  }
}

Input Schema

NameRequiredDescriptionDefault
catYescat
limitNolimit
x_paymentNoSigned x402 payment payload (optional; without it the answer is the price)

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?

With no annotations, the description carries the full burden and does disclose the non-obvious behavior: the call is metered at $0.003 USDC via x402, and without a signed `x_payment` payload the response is the price quote rather than data. Settlement (Coinbase) and the gateway path are named. It still omits what happens on insufficient/invalid payment or duplicate charges, but the paywall semantics are the critical disclosure here and they are present.

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

Conciseness3/5

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

Purpose and returned fields are front-loaded, which is correct. But the price is stated twice ('$0.003 via x402' and 'Pay 0.003 USDC'), and the full gateway URL with sample query string is inline bloat that could be trimmed without losing meaning.

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 3-param, no-annotation, no-output-schema tool, the description covers input domain, the item cap, the returned field list, and the payment flow — enough to invoke correctly and understand the response shape. The remaining gap is failure behavior after a paid call.

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 descriptions are pure placeholders ('cat', 'limit'), so the description does real work: it supplies valid category values and establishes that limit is bounded at 25 (the schema only says limit is a string, adding no bound). `x_payment` semantics come from the schema itself, so no loss there.

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+resource ('newest arXiv submissions in a category') and enumerates both the input domain (cs.AI, cs.CL, cs.LG, q-fin.TR, stat.ML) and the returned fields (id, title, authors, summary, published, PDF link). It is distinguishable from papers_search and papers_paper by being a recency feed rather than a query or single lookup, though it never names those siblings explicitly.

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 the example call (`?cat=cs.AI&limit=10`) and the 'up to 25' cap, which tells an agent how to shape a request. However, there is no statement of when to prefer this over papers_search or papers_paper, and no guidance on error or retry conditions after payment.

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