Skip to main content
Glama

Agent Exchange store

papers_search

$0.003 via x402: Search scholarly works by words (Crossref, relevance ranked), optionally from a year: up to 20 results with title, year, authors, venue, DOI, citation count, type and a link. Pay 0.003 USDC through https://store.agentexchange.work/gw/papers/search?q=self-consistency+language+models&since=2023 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": {
      "q": "<q>"
    },
    "name": "papers_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
qYesq
limitNoup to 20
sinceNopublication year from
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.6/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 most important trait: this is a paid tool ($0.003 via x402, USDC, settled by Coinbase) with a concrete gateway URL. It still omits rate limits, error/refund behavior, and pagination, but the monetization behavior is unusually well disclosed for an annotation-free tool.

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?

The cost and purpose are front-loaded, which is good, but the body is cluttered by a full gateway URL containing a hard-coded sample query and a redundant 'Via the Agent Exchange store gateway; settled by Coinbase' clause. Every sentence is not fully earning its place.

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?

There is no output schema, so the description usefully enumerates the returned fields (title, year, authors, venue, DOI, citation count, type, link) and the source (Crossref) and ranking (relevance). Complete enough to call correctly, though payment semantics for the optional x_payment parameter are only implicitly covered.

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 baseline is 3. The description adds marginal value by restating 'by words', 'optionally from a year', and 'up to 20 results', which loosely map to q, since and limit, but adds no syntax, format or default information beyond the schema.

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: 'Search scholarly works by words (Crossref, relevance ranked)', which clearly distinguishes it from a fetch-one-paper or reference-lookup tool. However, it never names or contrasts the sibling tools (papers_paper, papers_latest, papers_references, papers_verify), so differentiation must be inferred.

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 'Search scholarly works by words... optionally from a year', giving the agent a rough sense of when to reach for it. There is no explicit when-to-use/when-not guidance or reference to alternatives such as papers_latest or papers_paper, so routing is left to inference.

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