Skip to main content
Glama
Sign In
OpenAlex MCP Server

OpenAlex MCP Server

by SecretRichGarden
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

openalex_get_fulltext_sections

Retrieve specific sections from academic papers, including abstract, introduction, methods, results, discussion, conclusion, and references. Automatically downloads the paper if not yet cached.

Instructions

Get extracted sections (abstract, introduction, methods, results, discussion, etc.) from a downloaded paper. Will trigger download if not cached.

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_fulltext_sections"
  }
}

Input Schema

NameRequiredDescriptionDefault
work_idYesPaper identifier (OpenAlex ID, DOI, or PMID)
sectionsNoSpecific sections to retrieve (default: all available sections)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.6

TDQS

A3.9/5.0
Behavior4/5

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

Discloses that tool 'will trigger download if not cached', a key behavioral trait beyond what annotations provide (none given). No annotation contradiction. Could add more about side effects like network latency.

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 sentences, front-loaded with the main purpose, no superfluous words. Efficient and clear.

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?

Covers purpose and side effect but omits return format, handling of missing sections, and caching details. With no output schema, more detail on output would improve completeness.

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 covers 100% of parameters with descriptions. Description adds default behavior for sections (all available) and expands on accepted identifiers (OpenAlex ID, DOI, PMID), providing value beyond the schema.

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?

Description clearly states 'Get extracted sections from a downloaded paper' with a specific verb and resource. It also notes a side effect (trigger download if not cached), distinguishing it from sibling tools like openalex_download_fulltext and openalex_get_work.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus siblings, nor any when-not-to-use conditions. The description does not mention prerequisites or context for triggering downloads.

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