Skip to main content
Glama

search_papers

Search OpenAlex and arXiv for academic papers by keywords, DOI, or arXiv ID, with sorting by relevance or citation count to build reading lists and locate key references.

Instructions

Search open catalogs (OpenAlex + arXiv) for academic papers.

Use this first when the user needs papers, citations, or a reading list. Does not download PDFs. Prefer hits with pdf_url for the next step.

Ranking: pass sort=cited_by when the user wants the most cited / famous / popular papers. Pass sort=relevance (default) for topical match. Aliases like "most cited" are accepted; unknown values fall back to relevance.

A doi or arxiv_id looks up that paper (query may be empty). If query itself is a DOI or arXiv id, it is treated as a lookup, not keywords. Identifier filters win over a keyword query.

cited_by ranks on OpenAlex citation counts. arXiv keyword hits are skipped in that mode because they have no citation counts.

Possible error_code values: source_unavailable (one or both catalogs failed; remaining hits may still be useful). Empty papers is still status=ok.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
doiNoOptional DOI (`10.xxxx/...` or doi.org URL) to look up that work.
sortNo`relevance` or `cited_by` (aliases: citations, most_cited, famous).relevance
limitNoMaximum papers to return after merge (1–20, default 5).
queryNoKeywords, a bare DOI/arXiv id, or empty when doi/arxiv_id is set.
arxiv_idNoOptional arXiv id (`2301.12345`, `arxiv:…`, abs URL).
year_minNoInclusive publication/submission year floor. Impossible values (≤0, far future) are ignored.
open_access_onlyNoIf true (default), OpenAlex is restricted to OA; arXiv results are always included because they are OA.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
sortNorelevance
queryYes
papersNo
statusNook
messageNo
warningsNo
error_codeNo
Behavior5/5

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

With no annotations provided, the description carries the full burden, and it delivers: it discloses that PDFs are not downloaded, that identifier lookups override keyword queries, that arXiv keyword hits are skipped in cited_by mode, that unknown sort values fall back to relevance, and that error_code may be source_unavailable with possibly partial results. This is rich behavioral context beyond the bare operation.

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 description is well-structured and front-loaded, with the core purpose in the first sentence and usage guidance immediately after. Every paragraph adds useful information, though the ranking and identifier-lookup sections are somewhat dense and could be tightened without losing value.

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?

The description covers the essential context for a 7-parameter, zero-required tool with an output schema: when to use it, ranking semantics, identifier behavior, and possible error codes. It also notes that an empty papers list is still status=ok, which prevents misinterpreting valid empty results. The presence of an output schema means return-value documentation is not the description's responsibility.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, but the description adds meaning well beyond the schema. For sort, it explains aliases and fallback ('unknown values fall back to relevance'). For query, doi, and arxiv_id, it explains lookup behavior and precedence ('Identifier filters win over a keyword query'). This significantly aids correct invocation.

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 opens with a specific verb and resource: 'Search open catalogs (OpenAlex + arXiv) for academic papers.' It also distinguishes this tool from its siblings by stating it 'Does not download PDFs' and 'Use this first when the user needs papers, citations, or a reading list,' making it clear that search is the entry point while download/extraction/bibliography tools are separate follow-ups.

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?

The description gives explicit guidance: 'Use this first when the user needs papers, citations, or a reading list.' It also provides a clear when-not ('Does not download PDFs') and explains how to choose between sort modes ('pass sort=cited_by when the user wants the most cited / famous / popular papers'). It falls short of naming the alternative sibling tools explicitly, but the pipeline context is strong.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/benetche/ares-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server