Skip to main content
Glama
Sign In
openalex-mcp

openalex-mcp

by ckgerteis
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

oa_cited_by

Read-onlyIdempotent

Retrieve works that cite a specified OpenAlex work ID or DOI, ordered by citation count. Use it to trace downstream citations for a paper.

Instructions

Works that cite a given work, most-cited first. Returns the unified envelope. This is a filter on an identifier, not a term search, so no searched_for headline is set.

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": {
      "params": "<params>"
    },
    "name": "oa_cited_by"
  }
}

Input Schema

NameRequiredDescriptionDefault
paramsYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.3.0
    • addedInput schema / $defs / CitedByInput / properties / per_page / description
      Added value: +"Results per page (1-200). OpenAlex charges per call, not per result, so a sweep that will page through results should set 200."
  2. First observedv1.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, open-world, and non-destructive, so the safety profile is covered. The description adds genuinely new behavioral facts beyond that: the result ordering (most-cited first), that the response uses the unified envelope, and the subtle metadata detail that no searched_for headline is set for identifier filters.

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?

Three short sentences, front-loaded with what the tool returns and how it is sorted. The remaining sentences each carry distinct information (envelope format, identifier-vs-term filtering) with no repetition of the title or name.

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?

An output schema exists, so the description needn't explain return fields, and the envelope note is sufficient. Sorting, filter semantics, and the searched_for nuance give the agent what it needs to call and interpret this single-parameter tool; only the accepted identifier formats are left entirely to the schema.

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?

Reported top-level schema coverage is 0%, and the description only hints that the input is 'an identifier' without specifying accepted forms (OpenAlex work ID vs DOI). The nested schema does describe work_id and per_page, including the per-call billing rationale for per_page=200, so the gap is partly covered elsewhere, but the description itself adds little parameter meaning.

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?

The description names the exact resource (works that cite a given work) and adds a scope detail (most-cited first), so the agent knows precisely what comes back. It also contrasts itself with term search, which implicitly separates it from oa_search_works, though it never names that sibling explicitly.

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 clause 'this is a filter on an identifier, not a term search' implies the usage condition: use it when you already hold a work ID/DOI rather than keywords. However, there is no explicit when-not guidance, no mention of the alternative tool by name, and no note that an ID must be obtained first (e.g., via oa_search_works).

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