Skip to main content
Glama

get_openalex_references

OpenAlex: the works this one REFERENCES (its bibliography).

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_references"
  }
}

Input Schema

NameRequiredDescriptionDefault
work_idYes
max_resultsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full disclosure burden and provides almost none. It says nothing about ordering, pagination/truncation via max_results, return shape, or what happens with an invalid or non-existent work_id.

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?

A single short sentence with the key concept front-loaded and no padding. The leading 'OpenAlex:' prefix is mildly redundant with the tool name but costs only a few tokens.

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?

For a two-parameter tool with zero annotation and zero schema coverage and no output schema, the description is too thin: an agent cannot tell what the result items look like, how the result set is bounded, or how to form a valid work_id.

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%, so neither parameter is documented anywhere. The description does not explain the expected work_id format (e.g. OpenAlex work ID vs DOI) or what max_results caps, leaving both parameters semantically bare.

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 — the works this one REFERENCES — and the parenthetical '(its bibliography)' disambiguates the direction, which is the main confusion risk against citation-style siblings. It stops short of naming the sibling it is contrasted with, so an agent must infer that from the word 'REFERENCES' in caps.

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 definition tells you what it returns, so an agent can reason it should use this to find a paper's bibliography. There is no explicit when-to-use, when-not-to-use, or named alternative such as the citations counterpart for the opposite direction.

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.