Skip to main content
Glama

openalex_search_authors

Read-onlyIdempotent

Search OpenAlex for academic authors by name to find researcher profiles and return paginated results for identification.

Instructions

Search OpenAlex for academic authors by name.

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": {
      "query": "<query>"
    },
    "name": "openalex_search_authors"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesAuthor name to search.
per_pageNoResults per page (default 5, max 25).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.11

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is fully covered by structured data. The description adds nothing beyond them — no mention of result ordering, relevance behavior, rate limits, or that results are remote/third-party.

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 front-loaded sentence with zero filler. It is efficient, though so terse that no secondary information is delivered at all.

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 2-parameter read tool with full schema coverage and annotations, this is minimally viable. With no output schema, the description could have said what an author result contains (OpenAlex author IDs for follow-up lookups, works count, affiliation) — that omission matters for chaining.

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%, including the per_page default and max, so the baseline is 3. The description's 'by name' mildly reinforces that query is a name string rather than an ID, but adds no new syntax or matching semantics.

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 (search) and a specific resource (OpenAlex academic authors), scoped to name lookup. It implicitly separates itself from openalex_search_works, but never names or contrasts with the closer sibling dblp_search_authors.

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?

No guidance on when to choose this over openalex_search_works or dblp_search_authors, and no note on what a name query can or cannot resolve (e.g. ambiguity, affiliation disambiguation). The agent must infer usage entirely from the name.

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