Skip to main content
Glama

openalex_get_work

Read-onlyIdempotent

Retrieve full metadata for a scholarly work using its OpenAlex ID or DOI URL.

Instructions

Get full metadata for a scholarly work by OpenAlex ID or DOI.

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": {
      "id": "<id>"
    },
    "name": "openalex_get_work"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesOpenAlex ID (e.g. W2741809807) or DOI URL.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.11

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is covered. The description adds that it returns "full metadata," but says nothing beyond that about response shape, error behavior for unknown IDs, or rate limits.

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 zero filler. Every element (verb, scope, accepted identifier types) 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?

For a one-parameter read-only lookup with no output schema, the definition plus annotations give an agent enough to call it correctly. It stops short of describing the returned record or handling of invalid identifiers, keeping it at a 4.

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?

Schema description coverage is 100% and the single parameter's description already specifies the accepted formats (OpenAlex ID example W2741809807 or DOI URL). The description only restates that an ID or DOI is accepted, adding no format detail beyond the schema.

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 ("Get") and resource ("full metadata for a scholarly work") with a clear key (OpenAlex ID or DOI). It is distinguishable from openalex_search_works by returning a single work's full record, though it does not name 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?

Implies lookup-by-identifier usage via "by OpenAlex ID or DOI", but gives no guidance on when to use this versus openalex_search_works or crossref_get_work, and no prerequisites or exclusions.

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