Skip to main content
Glama

Agent Exchange store

papers_paper

$0.003 via x402: One paper in full by id (a DOI, an arXiv id like 2203.11171, or an OpenAlex W id): title, abstract, year, authors with institutions, venue, type, citation count, references count, open-access PDF URL, concepts. Pay 0.003 USDC through https://store.agentexchange.work/gw/papers/paper?id=2203.11171 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": {
      "id": "<id>"
    },
    "name": "papers_paper"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesid
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

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 burden and does disclose the key behavioral trait: this is a paid, x402-metered call costing $0.003 USDC, paid via the Agent Exchange gateway and settled by Coinbase; the schema also notes the no-payment path returns the price. Auth and settlement basics are covered, though rate limits, error/payment-failure behavior, and retry semantics are not.

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 price is front-loaded and the field list is efficient, but it is effectively one long run-on sentence packing cost, id formats, return fields, gateway URL, and settlement into a single breath. Slightly dense, though every clause carries information.

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?

No output schema exists, and the description compensates by listing the returned fields; the payment flow and the price-vs-result behavior of x_payment are also explained. Complete enough to call correctly, with only edge-case behavior (payment failure, duplicate ids across namespaces) left unstated.

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 coverage is 100%, so baseline is 3, but the description adds real meaning beyond the schema's bare 'id': it enumerates the accepted identifier forms (DOI, arXiv like 2203.11171, OpenAlex W id), which the schema does not specify. x_payment is left to the schema, which is adequate here.

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?

States a specific verb and resource ('One paper in full by id') and enumerates the returned fields (title, abstract, authors with institutions, venue, citation count, OA PDF URL, concepts). An agent can distinguish this from papers_search, papers_latest, and papers_references purely from the text.

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 is implied by the accepted id formats (DOI, arXiv id, OpenAlex W id), which tells the agent this is a direct lookup rather than a query tool. However, it never explicitly says when to use this over papers_search or papers_references, so no alternatives or exclusions are given.

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