Skip to main content
Glama

Paper search

paper_search
Read-onlyIdempotent

Academic and scientific paper search & DOI citation lookup across 250M+ works via OpenAlex (titles, authors, venues, citation counts, open-access PDF URLs, and abstracts). $0.002 per call over x402 (USDC on Arc, Base or Solana, or XNT on X1). Call once without payment for terms, then call again with payment.

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": "paper_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
qNoResearch topic search query (2-200 chars). Pass q OR doi.
doiNoExact DOI lookup (e.g. 10.48550/arxiv.2605.11781).
sortNoOptional sort: relevance (default), cited, or recent.
yearNoOptional 4-digit publication year filter.
limitNoOptional max papers to return (1-20, default 10).
paymentNosigned x402 payment payload (PAYMENT-SIGNATURE).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only declare it is a safe, open-world, idempotent read. The description adds what they cannot: a $0.002 per-call cost, the accepted payment rails (USDC on Arc/Base/Solana, XNT on X1), the underlying data provider, and the mandatory two-step payment handshake. That is exactly the behavioral context an agent needs before spending funds.

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?

Two dense sentences with the capability front-loaded and pricing/workflow trailing. Every clause carries information, though the parenthetical field list and multi-currency enumeration make the first sentence long enough to be slightly hard to scan.

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?

With no output schema, the description compensates by listing return fields (titles, authors, venues, citation counts, open-access PDF URLs, abstracts) and by fully specifying the payment lifecycle. Cost and data source are both disclosed, leaving nothing material an agent needs before a first 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 coverage is 100%, so the baseline is 3; the description earns a step above by explaining the `payment` parameter's operational role — it is absent on the first call and supplied on the second — which the schema's 'signed x402 payment payload' string does not convey. The q-vs-doi exclusivity is left to the schema.

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?

The description names a specific verb and resource — academic/scientific paper search plus exact DOI citation lookup — and scopes it to 250M+ works via OpenAlex, enumerating the fields returned. This is precise enough that an agent can separate it from market/agora/agent-marketplace siblings without opening the schema.

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 gives explicit operational guidance: call once without `payment` for terms, then call again with `payment`. That resolves the biggest usage ambiguity for a paid endpoint. It does not state when to prefer this over other search siblings, but no exclusions are needed for correct invocation.

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