Skip to main content
Glama

get_openalex_citations

OpenAlex: papers that CITE this work (forward citation graph), most-cited first.

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": "get_openalex_citations"
  }
}

Input Schema

NameRequiredDescriptionDefault
startNo
work_idYes
max_resultsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It usefully discloses result ordering ('most-cited first'), which is real behavioral information, but says nothing about pagination behavior via start/max_results, total-count/truncation behavior, whether the call is read-only, or what the returned records contain.

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?

A single front-loaded sentence with the source, the operation, the graph direction, and the ordering — no filler, nothing to cut.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema, no annotations, and 0% parameter documentation leave the definition too thin for a tool whose correctness hinges on the work_id format and on how paging interacts with a 'most-cited first' ordering.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across three parameters, so the description must compensate and does not. The critical ambiguity for work_id (OpenAlex ID vs DOI vs URL) is unaddressed, and start/max_results paging semantics are left entirely to defaults.

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?

Names a specific verb+resource: 'papers that CITE this work', plus the graph direction ('forward citation graph') and result ordering ('most-cited first'). That is enough for an agent to distinguish it from a backward-reference tool, though it never names the sibling (get_openalex_references) 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?

Usage is only implied: the phrase 'forward citation graph' signals the contrast with looking up references, but the description never states when to choose this over get_openalex_references or get_paper_citations, nor any prerequisites.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.