Skip to main content
Glama
niol-zh

research-mcp

by niol-zh
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

get_citing_papers

Retrieve citing papers for a document using its DOI or OpenAlex ID, sorted by citation count. Uses OpenAlex by default; Scopus requires institutional access.

Instructions

Forward citations: papers that CITE a given document, most-cited first. Defaults to OpenAlex (free, no quota, wide coverage, accepts a DOI or OpenAlex ID). source='scopus' uses REFEID(), a restricted field that only works with an institutional Scopus subscription.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sortNoSort by 'coverDate' or 'relevancy'.coverDate
countNoResults to return (default 5, max 25).
sourceNoWhich database to query. Default 'openalex'; 'scopus' requires an institutional subscription.openalex
scopus_idYesDocument identifier: a DOI or OpenAlex work ID (default OpenAlex source), or a Scopus ID.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.5.1
    • changedInput schema / properties / scopus_id / description
      Previous value: -"Scopus ID of the document."New value: +"Document identifier: a DOI or OpenAlex work ID (default OpenAlex source), or a Scopus ID."
    • addedInput schema / properties / source
      Added value: +{
+  "default": "openalex",
+  "description": "Which database to query. Default 'openalex'; 'scopus' requires an institutional subscription.",
+  "enum": [
+    "openalex",
+    "scopus"
+  ],
+  "type": "string"
+}
  2. First observedv0.4.0

TDQS

A4.4/5.0
Behavior4/5

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

No annotations are provided, but the description discloses an important constraint: the 'scopus' source requires an institutional subscription and uses a restricted field (REFEID). This covers a key behavioral caveat.

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?

Description is concise and well-structured, conveying essential information in three sentences without redundancy or unnecessary detail.

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?

Tool is simple and the description provides enough context for correct invocation, including source selection, identifier types, and ordering. No output schema is present, but the description sufficiently frames expected results.

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 all parameters with descriptions. The description adds context about the identifier formats (DOI, OpenAlex ID, Scopus ID), default source, and sort options, enhancing understanding 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 the tool returns forward citations (papers citing a given document) and specifies ordering (most-cited first). It distinguishes from siblings like get_references (backward citations) and search_scopus.

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 guidance on default source (OpenAlex) and when to use the alternative source ('scopus' requires institutional subscription). Implicitly indicates use case for forward citation lookup, though no explicit comparison to all siblings.

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