Skip to main content
Glama

Search scholarly works by topic with citations and OA links

research_papers
Read-only

Searches OpenAlex (CC0) for scholarly works: title, authors with institutions, year, venue, DOI, open-access PDF link, citation count, topic and abstract (max 2,000 characters). Filters: publication year range, open access only, minimum citations; sort by relevance, citations or date (citations and date search the words as one phrase). Limit max 25. Price: $0.002 per successful call, paid with x402 (USDC on Base, Solana and 10 more networks); failed calls are not charged.

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

Input Schema

NameRequiredDescriptionDefault
qYesSearch words (1-200 characters)
sortNorelevance (default), citations or date
limitNoResults, 1-25 (default 10)
toYearNoLatest publication year (optional)
fromYearNoEarliest publication year (optional)
openAccessNoOnly open-access works (default false)
minCitationsNoMinimum citation count (default 0)

Output Schema

NameRequiredDescriptionDefault
sortNo
countNo
queryNo
totalNo
sourceNo
resultsNo
checkedAtNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint and openWorldHint, so the description's main added value is the cost model: $0.002 per successful call via x402 USDC on Base, Solana and 10 more networks, with failed calls free. It also discloses the 25-result ceiling and the 2,000-character abstract truncation. It does not explain payment flow mechanics or rate limiting, so it is good but not exhaustive beyond the annotations.

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?

Front-loads the purpose, then returned fields, then filters, then pricing — a sensible order with almost no wasted words. It is dense and relies on semicolons to cram several facts into one long sentence, which slightly hurts scannability.

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 seven-parameter read-only search with full schema coverage and an output schema, nothing essential is missing: scope, filters, sort semantics, result cap, return fields, and billing are all covered.

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 would be 3, but the description adds real meaning on top: the phrase-matching behavior for the citations/date sort modes and the maximum 25 limit are not stated in the schema's own parameter descriptions. The optional filters are merely restated, which is why it isn't a 5.

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 ('Searches OpenAlex (CC0) for scholarly works') and enumerates exactly what comes back: title, authors with institutions, year, venue, DOI, OA PDF link, citation count, topic, abstract. That is far more specific than the title alone and clearly separates it from generic search siblings like links or apps_search.

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?

Gives concrete context for when it applies: scholarly literature with year-range, open-access-only, and minimum-citation filters, plus a non-obvious caveat that 'citations' and 'date' sorts search the words as one phrase. It stops short of naming an alternative (e.g., arxiv, pm_search, doi) or stating exclusions, so an agent must infer routing itself.

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