Skip to main content
Glama
oksure

OpenAlex Research MCP Server

by oksure

search_by_topic

Search scholarly works by research topic. Filter by venue, year, citation count, institution, and more. Supports exact phrase matching and field-specific searches for precise literature discovery.

Instructions

Search for works within specific research topics or domains. Use this to explore literature in a particular field or subfield. Supports venue filtering to restrict results to top journals/conferences.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
topicYesTopic name or keywords to search for (e.g., "artificial intelligence", "climate change", "quantum computing"). For exact phrase matching (e.g., 'privacy paradox' as a specific concept), set exact_phrase to true.
exact_phraseNoSet to true for exact phrase matching. Without this, search terms are matched independently. Use this when searching for a specific concept or multi-word term (e.g., 'privacy paradox', 'supply chain resilience').
search_fieldNoRestrict search to a specific field: 'title' (paper titles only), 'abstract' (abstracts only), or 'fulltext' (full text only). By default, searches across all fields. Cannot be combined with exact_phrase.
from_yearNoFilter works from this year onwards
to_yearNoFilter works up to this year
source_nameNoRestrict to a specific journal or conference by name (e.g., "Nature", "ICML", "PNAS")
source_issnNoRestrict to a specific journal/conference by ISSN (most precise)
min_citationsNoMinimum citation count threshold to filter low-impact papers
author_institutionNoFilter by author institution (exact OpenAlex display_name). Use | for OR, e.g., "Harvard University|Stanford University"
institution_groupNoNamed institution group preset. Options: harvard_stanford_mit, ivy_league, top_us, top_us_business, insead_london, top_global_business, top_china. Use list_journal_presets to see all.
sortNoSort by: cited_by_count:desc, publication_year:desc, relevance_score (default)
per_pageNoResults per page (default: 10, use 20 for broader coverage, max 200)
Behavior3/5

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

No annotations are provided, so the description carries full burden. It discloses basic functionality and venue filtering but omits details like pagination behavior, default sorting, rate limits, or what the return format looks like. The description is adequate but not rich.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is two concise sentences: first states purpose, second adds a key capability. Every sentence earns its place, and the information is front-loaded with no wasted words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with 12 parameters and no output schema, the description is too brief. It covers the main purpose and one extra feature but lacks details on return behavior, pagination, or sorting defaults. Not fully complete for an agent to use correctly.

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 coverage is 100%, so the schema already documents all parameters. The description adds marginal context (e.g., exact phrase matching, venue filtering) but does not significantly enhance understanding beyond the schema. Baseline score of 3 is appropriate.

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 clearly states 'Search for works within specific research topics or domains' using a specific verb and resource. It distinguishes from siblings like 'search_works' and 'search_works_in_venue' by emphasizing topic-based search and venue filtering.

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 advises 'Use this to explore literature in a particular field or subfield' and mentions venue filtering. However, it does not explicitly state when to use alternatives like 'search_works' or when not to use this tool, leaving room for ambiguity.

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/oksure/openalex-research-mcp'

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