Skip to main content
Glama
reetp14

OpenAlex MCP Server

by reetp14

search_authors

Find academic authors and researchers by name, institution, ORCID, or other criteria using OpenAlex's comprehensive scholarly database.

Instructions

Search authors and researchers

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
searchNoFull-text search query
filterNoKey:value OpenAlex filters. Supports entity attributes (e.g., 'orcid', 'last_known_institution.id'), IDs, and convenience filters (e.g., 'display_name.search'). Example: 'has_orcid:true,last_known_institution.country_code:US'
sortNoSort field with optional :desc
pageNoPage number
per_pageNoResults per page (max 200)
cursorNoCursor for deep pagination
group_byNoGroup results by field
selectNoFields to return
sampleNoRandom sample size
seedNoRandom seed
mailtoNoEmail for rate limits
api_keyNoPremium API key

Implementation Reference

  • The handler function that implements the core logic of the 'search_authors' tool. It calls the makeOpenAlexRequest helper with the '/authors' endpoint and the input arguments, then formats the response as MCP content.
    export async function searchAuthors(args: any) {
        return {
            content: [{
                    type: "text",
                    text: JSON.stringify(await makeOpenAlexRequest("/authors", args), null, 2)
                }]
        };
    }
  • The input schema defining the parameters accepted by the 'search_authors' tool, including search, filter, pagination, and API options.
        inputSchema: {
            type: "object",
            properties: {
                search: { type: "string", description: "Full-text search query" },
                filter: { type: "string", description: "Key:value OpenAlex filters. Supports entity attributes (e.g., 'orcid', 'last_known_institution.id'), IDs, and convenience filters (e.g., 'display_name.search'). Example: 'has_orcid:true,last_known_institution.country_code:US'" },
                sort: { type: "string", description: "Sort field with optional :desc" },
                page: { type: "number", description: "Page number" },
                per_page: { type: "number", description: "Results per page (max 200)" },
                cursor: { type: "string", description: "Cursor for deep pagination" },
                group_by: { type: "string", description: "Group results by field" },
                select: { type: "string", description: "Fields to return" },
                sample: { type: "number", description: "Random sample size" },
                seed: { type: "number", description: "Random seed" },
                mailto: { type: "string", description: "Email for rate limits" },
                api_key: { type: "string", description: "Premium API key" }
            }
        }
    },
  • src/index.ts:283-284 (registration)
    The switch case in the CallToolRequest handler that registers and routes execution to the searchAuthors handler for 'search_authors' tool calls.
    case "search_authors":
        return await searchAuthors(args);
  • src/index.ts:78-98 (registration)
    The tool object in the ListTools response that registers 'search_authors' with its name, description, and schema.
    {
        name: "search_authors",
        description: "Search authors and researchers",
        inputSchema: {
            type: "object",
            properties: {
                search: { type: "string", description: "Full-text search query" },
                filter: { type: "string", description: "Key:value OpenAlex filters. Supports entity attributes (e.g., 'orcid', 'last_known_institution.id'), IDs, and convenience filters (e.g., 'display_name.search'). Example: 'has_orcid:true,last_known_institution.country_code:US'" },
                sort: { type: "string", description: "Sort field with optional :desc" },
                page: { type: "number", description: "Page number" },
                per_page: { type: "number", description: "Results per page (max 200)" },
                cursor: { type: "string", description: "Cursor for deep pagination" },
                group_by: { type: "string", description: "Group results by field" },
                select: { type: "string", description: "Fields to return" },
                sample: { type: "number", description: "Random sample size" },
                seed: { type: "number", description: "Random seed" },
                mailto: { type: "string", description: "Email for rate limits" },
                api_key: { type: "string", description: "Premium API key" }
            }
        }
    },
  • The shared helper function used by the search_authors handler (and other tools) to make HTTP requests to the OpenAlex API, handling query params, headers, auth, and errors.
    export async function makeOpenAlexRequest(endpoint: string, params: OpenAlexQueryParams = {}): Promise<any> {
        const queryString = buildQueryString(params);
        const url = `${OPENALEX_BASE_URL}${endpoint}${queryString ? '?' + queryString : ''}`;
        try {
            // Build User-Agent with mailto for polite pool access
            let userAgent = 'OpenAlex-MCP-Server/1.0.0 (https://github.com/openalex-mcp-server)';
            if (params.mailto) {
                userAgent += ` mailto:${params.mailto}`;
            }
            else {
                // Use environment variable for default email
                const defaultEmail = process.env.OPENALEX_DEFAULT_EMAIL || 'mcp-server@example.com';
                userAgent += ` mailto:${defaultEmail}`;
            }
    
            // Build headers
            const headers: Record<string, string> = {
                'Accept': 'application/json',
                'User-Agent': userAgent
            };
    
            // Add Bearer token - check parameter first, then environment variable
            const bearerToken = params.bearer_token || process.env.OPENALEX_BEARER_TOKEN;
            if (bearerToken) {
                headers['Authorization'] = `Bearer ${bearerToken}`;
            }
    
            const response = await axios.get(url, {
                headers,
                timeout: 30000
            });
            return response.data;
        }
        catch (error) {
            if (axios.isAxiosError(error)) {
                throw new Error(`OpenAlex API error: ${error.response?.status} - ${error.response?.statusText || error.message}`);
            }
            throw error;
        }
    }
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure but offers minimal information. It doesn't mention rate limits (though 'mailto' parameter hints at them), authentication requirements (though 'api_key' parameter suggests premium access), pagination behavior, or what constitutes a successful search result. The description is too brief to adequately inform about the tool's operational characteristics.

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?

The description is extremely concise at just three words, with zero wasted language. It's front-loaded with the essential action and target. While it may be too brief for completeness, it earns full marks for conciseness as every word serves a clear purpose.

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 complex tool with 12 parameters, no annotations, and no output schema, the description is insufficiently complete. It doesn't explain what constitutes a successful search, what format results return, how pagination works, or any behavioral constraints. The agent would need to infer much from the parameter descriptions alone, which is inadequate for a search tool of this complexity.

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?

With 100% schema description coverage, the input schema already documents all 12 parameters thoroughly. The description adds no additional parameter information beyond what's in the schema. According to scoring rules, when schema coverage is high (>80%), the baseline is 3 even with no parameter information in the description.

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 'Search authors and researchers' clearly states the verb (search) and resource (authors/researchers), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'get_entity' or 'autocomplete' which might also retrieve author information, so it doesn't achieve full sibling differentiation.

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 provides no guidance on when to use this tool versus alternatives. There are multiple sibling search tools (search_funders, search_institutions, etc.) and retrieval tools (get_entity, autocomplete), but the description offers no context about when this specific author search is appropriate versus other approaches.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/reetp14/openalex-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server