Skip to main content
Glama
michalhron

Scopus Plus MCP

by michalhron
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

search_all

Search academic literature across Scopus or OpenAlex and automatically page through results to retrieve up to a specified maximum in a single call.

Instructions

Search Scopus (or OpenAlex with source='openalex') and page through results automatically, returning up to max_results entries in one call. Scopus pages hold SCOPUS_PAGE_SIZE records (default 25) and switch to cursor paging beyond 5,000; OpenAlex pages hold 200. Results over 50 records are written to disk as JSON and CSV. Large max_results values consume significant quota — use conservatively.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sortNoSort order (e.g., 'coverDate', 'relevancy', 'citedby'). Defaults to 'coverDate' for Scopus, 'relevance' for OpenAlex.
queryYesSearch query. Scopus: Scopus syntax (e.g., 'TITLE(AI) AND PUBYEAR > 2020'). OpenAlex: plain words matched against title and abstract; quote phrases (e.g., '"organizing vision"').
scopeNoRestrict to journals, by ISSN: a list of ISSNs, or a basket name ('basket_of_eight' / 'ais8': the AIS Senior Scholars' Basket of Eight). ISSNs are used rather than journal names, which Scopus spells inconsistently.
inlineNoWhat comes back in the reply when results go to files (over 50 records). 'sample' (default): the first 10. 'compact': every record as one JSON line of key fields (IDs, DOI, year, first author, title, venue, ISSN, citations): use it when the caller cannot read the server's files, e.g. from a cloud session. 'full': every record in full (large).sample
sourceNoData source. 'scopus' (default) needs subscriber entitlement for search, citations and references. 'openalex' needs none: IDs may be DOIs, OpenAlex work IDs (W...), or Scopus IDs (resolved to a DOI via Scopus metadata), and results carry OpenAlex IDs. Never mix sources within one analysis.scopus
max_resultsNoMaximum total results to fetch across all pages (default 200). Large values consume quota.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses page sizes (25 Scopus, cursor paging past 5,000, 200 OpenAlex), the 50-record threshold above which results are written to disk as JSON/CSV, the entitled-subscriber requirement for Scopus, and quota cost. It omits error/truncation behavior and what happens when max_results exceeds available pages.

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?

Four sentences, front-loaded with the core action and scope, then pagination internals, then the quota caveat. Dense with numbers but each sentence earns its place; no marketing filler.

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?

For a 6-parameter search tool with 100% schema coverage and no output schema, the description covers the non-obvious operational facts an agent needs: paging limits, disk-write threshold, inline fallbacks, and quota risk. Only edge-case behavior (errors, empty results) is left unexplained.

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 description coverage is 100%, so the schema already documents all six parameters. The description reinforces max_results with a quota caveat and source with a 'never mix sources' rule, but adds no syntax or format detail beyond what the schema provides, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Search Scopus ... or OpenAlex') plus the distinguishing behavior ('page through results automatically, returning up to max_results entries in one call'). It never names the sibling search_scopus, so the agent must infer why this differs from a plain single-source search.

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?

Gives real selection guidance: use source='openalex' when no subscriber entitlement exists, use inline modes when the caller cannot read server files, and a caution to use large max_results conservatively due to quota. It stops short of naming alternatives like search_scopus or stating when-not-to-use this tool.

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