Skip to main content
Glama

search_openalex_authors

OpenAlex: search authors; returns profiles with h-index, i10-index, works/citation counts and institutions.

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

Input Schema

NameRequiredDescriptionDefault
queryYes
startNo
max_resultsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full burden; it does disclose the return shape (profiles with h-index, i10-index, works/citation counts, institutions), which is real behavioral value. It says nothing about read-only nature, rate limits, pagination across results, or empty-result behavior.

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?

One short sentence, front-loaded with the action and namespace, followed immediately by the return contents. No filler, though it is arguably too terse given the undocumented parameters.

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 simple three-parameter search with no output schema, describing the returned profile fields covers the main gap. However, pagination semantics and query construction are unaddressed, which matters for a search tool whose whole job is result retrieval.

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% and the description adds no meaning for any of the three parameters. "query" syntax (name vs ORCID vs affiliation), "start" offset, and "max_results" limits are all undocumented, leaving the agent to guess from parameter names and defaults alone.

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 and resource ("search authors") and enumerates what a result profile contains (h-index, i10-index, works/citation counts, institutions), so the agent knows the payload shape. It does not explicitly contrast itself with get_author or search_authors, so sibling differentiation is left implicit.

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?

There is no when-to-use statement and no alternatives named: nothing tells the agent to prefer get_author when an OpenAlex ID is already known, or to switch to search_openalex_works for papers. Usage is only inferable from the word "search".

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.