scopus-mcp

Overview Schema Source Related Servers Discussions Admin

scopus_search

Read-onlyIdempotent

Search the Scopus academic database with Boolean queries to find papers by title, abstract, keywords, author, affiliation, year, or document type.

Instructions

Search the Scopus academic database for papers using Boolean query syntax.

Common field codes:

TITLE-ABS-KEY(term) — search title, abstract, and keywords (most useful)
TITLE(term) — title only
AUTH(name) — author name, e.g. AUTH("Smith J")
AFFIL(institution) — author affiliation
PUBYEAR > 2020 — filter by publication year
DOCTYPE(ar) — document type: ar=article, re=review, cp=conference paper

Boolean operators: AND, OR, AND NOT Example: TITLE-ABS-KEY("machine learning" AND cancer) AND PUBYEAR > 2020

Read the scopus://search-syntax resource for the full syntax reference.

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": {
      "query": "<query>"
    },
    "name": "scopus_search"
  }
}

Input Schema

Name	Required	Description	Default
`view`	No	Response detail: STANDARD or COMPLETE	STANDARD
`count`	No	Number of results to return (1–25)
`query`	Yes	Scopus Boolean search query
`start`	No	Pagination offset (0-based)

Output Schema

Name	Required	Default
`query`	No
`papers`	Yes
`source`	No	scopus
`showing`	Yes
`served_at`	No
`truncated`	No
`next_start`	No
`start_index`	No
`stop_reason`	No	complete
`retrieved_at`	No
`total_results`	Yes
`items_per_page`	No
`complete_corpus`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedNov 6, 2026

addedInput schema / properties / start / maximum
```
Added value: +4999
```

addedInput schema / properties / view / enum

Added value: +[
+  "STANDARD",
+  "COMPLETE"
+]

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$defs": {
+    "Paper": {
+      "additionalProperties": true,
+      "properties": {
+        "cited_by_count": {
+          "anyOf": [
+            {
+              "type": "integer"
+            },
+            {
+              "type": "null"
+            }
+          ],
+          "default": null,
+          "title": "Cited By Count"
+        },
+        "cover_date": {
+          "default": "",
+          "title": "Cover Date",
+          "type": "string"
+        },
+        "doi": {
+          "anyOf": [
+            {
+              "type": "string"
+            },
+            {
+              "type": "null"
+            }
+          ],
+          "default": null,
+          "title": "Doi"
+        },
+        "open_access": {
+          "anyOf": [
+            {
+              "type": "boolean"
+            },
+            {
+              "type": "null"
+            }
+          ],
+          "default": null,
+          "title": "Open Access"
+        },
+        "publication": {
+          "default": "",
+          "title": "Publication",
+          "type": "string"
+        },
+        "retrieved_at": {
+          "anyOf": [
+            {
+              "type": "string"
+            },
+            {
+              "type": "null"
+            }
+          ],
+          "default": null,
+          "title": "Retrieved At"
+        },
+        "scopus_id": {
+          "default": "",
+          "title": "Scopus Id",
+          "type": "string"
+        },
+        "served_at": {
+          "anyOf": [
+            {
+              "type": "string"
+            },
+            {
+              "type": "null"
+            }
+          ],
+          "default": null,
+          "title": "Served At"
+        },
+        "source": {
+          "default": "scopus",
+          "title": "Source",
+          "type": "string"
+        },
+        "title": {
+          "default": "",
+          "title": "Title",
+          "type": "string"
+        }
+      },
+      "title": "Paper",
+      "type": "object"
+    }
+  },
+  "additionalProperties": true,
+  "properties": {
+    "complete_corpus": {
+      "default": false,
+      "title": "Complete Corpus",
+      "type": "boolean"
+    },
+    "items_per_page": {
+      "default": 0,
+      "title": "Items Per Page",
+      "type": "integer"
+    },
+    "next_start": {
+      "anyOf": [
+        {
+          "type": "integer"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "default": null,
+      "title": "Next Start"
+    },
+    "papers": {
+      "items": {
+        "$ref": "#/$defs/Paper"
+      },
+      "title": "Papers",
+      "type": "array"
+    },
+    "query": {
+      "default": "",
+      "title": "Query",
+      "type": "string"
+    },
+    "retrieved_at": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "default": null,
+      "title": "Retrieved At"
+    },
+    "served_at": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "default": null,
+      "title": "Served At"
+    },
+    "showing": {
+      "title": "Showing",
+      "type": "integer"
+    },
+    "source": {
+      "default": "scopus",
+      "title": "Source",
+      "type": "string"
+    },
+    "start_index": {
+      "default": 0,
+      "title": "Start Index",
+      "type": "integer"
+    },
+    "stop_reason": {
+      "default": "complete",
+      "title": "Stop Reason",
+      "type": "string"
+    },
+    "total_results": {
+      "title": "Total Results",
+      "type": "integer"
+    },
+    "truncated": {
+      "default": false,
+      "title": "Truncated",
+      "type": "boolean"
+    }
+  },
+  "required": [
+    "total_results",
+    "showing",
+    "papers"
+  ],
+  "title": "PaperSearchResult",
+  "type": "object"
+}

First observedv0.1.0Jun 23, 2026

TDQS

A3.9/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is fully covered by structured data. The description adds nothing beyond that: it does not mention authentication/entitlement requirements (notably whether scopus_check_access must be run first), rate limits, or what COMPLETE view actually changes. Return shape is covered by the output schema, so the remaining gap is moderate rather than severe.

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?

The purpose sentence is front-loaded and the field-code list is scannable, with a single compact example. There is minor redundancy in enumerating syntax codes and then deferring to the scopus://search-syntax resource, but the content largely earns its place.

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?

With a full output schema, complete parameter descriptions, and rich annotations, the only thing an agent genuinely lacks is tool-selection guidance relative to the many sibling search/get tools and any access prerequisite. Query construction — the highest-risk part of calling this tool — is well covered.

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 coverage is 100%, so the baseline would be 3, but the description meaningfully enriches the required `query` parameter with field codes, Boolean operators, and a concrete example — far beyond "Scopus Boolean search query". It does not clarify the STANDARD vs COMPLETE trade-off or how `start`/`count` interact with the 25-result ceiling, leaving those to 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?

States a specific verb and resource ("Search the Scopus academic database for papers") and the scope word "papers" implicitly separates it from scopus_search_authors and scopus_search_affiliations. An agent can identify the intended tool without opening the schema.

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?

The description is entirely about how to construct a query, not about when to choose this tool over scopus_search_authors, scopus_get_abstracts, or scopus_analyze_results, and it never says when NOT to use it. It does flag TITLE-ABS-KEY as "most useful" and gives a worked example, which supplies implied usage context but no real routing guidance.

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

Deploy Server