Skip to main content
Glama
Sign In
OpenAlex MCP Server

OpenAlex MCP Server

by SecretRichGarden
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

openalex_get_work

Retrieve detailed paper information including abstract, authors, topics, and reference count using OpenAlex ID, DOI, or PMID.

Instructions

Get detailed information about a specific paper by its OpenAlex ID, DOI, or PMID. Includes full abstract, author information, topics, and references count.

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": {
      "work_id": "<work_id>"
    },
    "name": "openalex_get_work"
  }
}

Input Schema

NameRequiredDescriptionDefault
work_idYesPaper identifier (OpenAlex ID like W1234567890, DOI like 10.xxx, or PMID)
include_abstractNoInclude abstract in response (default: true)
abstract_modeNoAbstract processing mode: "quick" (cached) or "deep" (fetch new)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.6

TDQS

A3.8/5.0
Behavior3/5

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

No annotations exist, so description carries full burden. It lists returned fields but does not disclose behavioral traits like caching, abstract mode differences (quick vs deep), or any side effects. Basic coverage but lacks depth.

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?

Single sentence, front-loaded with action and resource, no redundant words. Efficient and clear.

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?

Given no output schema, the description helps by listing included fields (abstract, author, topics, references count). However, it omits explanation of abstract modes and response format details. Nearly complete.

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 baseline 3. The description adds context about returned content but does not enhance parameter meaning beyond what the schema already provides.

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 verb 'get' and resource 'paper', specifies three identifier types (OpenAlex ID, DOI, PMID), and differentiates from sibling batch tool by focusing on a single work.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied for single paper retrieval, but no explicit when-to-use or alternatives guidance is given. The sibling tool openalex_batch_get_works suggests batch use, but the description does not clarify when to choose this tool over the batch one.

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

Deploy Server

Other Tools