Skip to main content
Glama
reetp14

OpenAlex MCP Server

by reetp14

search_sources

Search academic journals and sources in OpenAlex's scholarly database using queries, filters, and sorting to find relevant publications for research.

Instructions

Search journals and sources

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
searchNoFull-text search query
filterNoKey:value OpenAlex filters. Supports entity attributes (e.g., 'issn', 'country_code', 'is_oa'), IDs, and convenience filters (e.g., 'display_name.search'). Example: 'is_oa:true,type:journal'
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 core handler function that implements the logic for the 'search_sources' tool. It invokes the OpenAlex API for sources using makeOpenAlexRequest and formats the response as MCP content.
    export async function searchSources(args: any) {
        return {
            content: [{
                    type: "text",
                    text: JSON.stringify(await makeOpenAlexRequest("/sources", args), null, 2)
                }]
        };
    }
  • The input schema and metadata definition for the 'search_sources' tool, provided in the listTools response.
    {
        name: "search_sources",
        description: "Search journals and sources",
        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., 'issn', 'country_code', 'is_oa'), IDs, and convenience filters (e.g., 'display_name.search'). Example: 'is_oa:true,type:journal'" },
                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:285-286 (registration)
    Registers the handler by dispatching 'search_sources' tool calls to the searchSources function in the CallToolRequest handler.
    case "search_sources":
        return await searchSources(args);
  • src/index.ts:24-24 (registration)
    Imports the searchSources handler function for use in the MCP server.
    import { searchSources } from "./tools/searchSources.js";
Behavior2/5

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

No annotations are provided, so the description carries full burden for behavioral disclosure. It mentions 'search' but doesn't describe key behaviors: whether this is a read-only operation, rate limits (though 'mailto' parameter hints at this), pagination behavior, or what the output looks like. The description is minimal and fails to compensate for the lack of annotations.

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—just three words—with zero wasted text. It's front-loaded and efficiently states the core function. However, this conciseness comes at the cost of completeness, but for this dimension alone, it scores highly.

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?

Given the complexity (12 parameters, no annotations, no output schema), the description is incomplete. It doesn't explain the tool's scope, behavioral traits, or output format. While the schema covers parameters well, the description fails to provide necessary context for a search tool with many options and no structured output information.

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%, with detailed parameter descriptions in the input schema (e.g., 'Full-text search query' for 'search', 'Key:value OpenAlex filters' for 'filter'). The description adds no parameter-specific information beyond what's in the schema. According to rules, with high schema coverage (>80%), the baseline is 3 even with no param info in the description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Search journals and sources' states the action (search) and target resources (journals and sources), providing a basic purpose. However, it's vague about what 'sources' encompasses and doesn't distinguish this tool from sibling search tools like search_authors, search_works, etc., which all search different entity types. It lacks specificity about what makes this search unique.

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. With multiple sibling search tools (e.g., search_authors, search_works), there's no indication that this is for journals/sources specifically, nor any context about prerequisites or exclusions. Usage is implied by the name but not explicitly stated in the description.

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