Skip to main content
Glama
oksure

OpenAlex Research MCP Server

by oksure

find_seminal_papers

Identify seminal papers published more than five years ago with high citations to find foundational works and meet reviewer expectations.

Instructions

Find seminal/foundational papers in a research area — those published more than 5 years ago with very high citations. These are the "must-cite" papers that establish the intellectual lineage of a field. Use to identify citations that reviewers expect to see.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesResearch topic or concept. 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.
min_citationsNoMinimum citation count (default: 200 since these are foundational papers)
published_beforeNoOnly papers published before this year (default: current year - 5)
source_nameNoRestrict to a specific venue (e.g., "Nature", "Science", "NeurIPS")
per_pageNoResults per page (default: 10, max: 50)
Behavior3/5

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

No annotations provided; description discloses defaults for min_citations and published_before and clarifies the 'seminal' concept, but does not detail sorting, pagination behavior, or output structure beyond per_page max.

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?

Two concise sentences plus a usage statement; each sentence adds value without redundancy, front-loaded with key purpose.

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?

Adequately complete given 7 params and no output schema: explains defaults, semantics, and use case. Could detail output format but not required.

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% with good parameter descriptions; the main description does not add meaning beyond what's already in the schema, earning the baseline score.

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 the tool finds seminal/foundational papers with constraints (older than 5 years, high citations) and distinguishes itself by emphasizing 'must-cite' papers, differentiating from generic search tools like search_works.

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?

Provides explicit usage context ('Use to identify citations that reviewers expect to see') but lacks explicit when-not-to-use or alternatives, though the context is clear enough for agents to infer.

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