Skip to main content
Glama
Sign In
openalex-mcp

openalex-mcp

by ckgerteis
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

oa_search_authors

Read-onlyIdempotent

Search OpenAlex for authors by name and return matching records with affiliations, publication and citation counts, and h-index. Filter by institution or paginate through results.

Instructions

Search OpenAlex for authors by name. Returns the unified envelope; each item is an author record (record_type author) with affiliations, work and citation counts, and h-index in extra.

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

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 / AuthorSearchInput / 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. Changed1 schema field changedv2.2.0
    • addedInput schema / $defs / AuthorSearchInput / properties / query / maxLength
      Added value: +2000
  3. First observedv1.1.0

TDQS

B3/5.0
Behavior3/5

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

The annotations already establish that this is a read-only, idempotent, non-destructive open-world search. The description adds useful output context about the unified envelope and author record fields, but it does not disclose operational details such as rate-limit behavior or pagination constraints beyond what the schema already says.

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?

The definition is compact and front-loads the core action. The second sentence adds useful return-shape context, though it partially duplicates what the output schema can provide.

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

Completeness3/5

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

For a read-only search with annotations and an output schema, the description covers the basic action and return structure. It is still incomplete for routing between oa_search_authors and oa_get_author, and it does not explain available filtering behavior.

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?

The description only clarifies the name-search aspect of the required query. With schema description coverage reported as 0%, it does not compensate for other parameters such as institution filtering or page sizing, leaving the agent reliant on 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?

The description states a specific verb and resource: 'Search OpenAlex for authors by name.' This clearly distinguishes the tool from sibling search tools for works, sources, and institutions, though it does not explicitly distinguish it from oa_get_author.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies that this is a name-based author search but gives no explicit when-to-use guidance, exclusions, or comparison with alternatives such as oa_get_author. The agent must infer the routing decision from the tool name and sibling list.

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