Skip to main content
Glama
Sign In
openalex-mcp

openalex-mcp

by ckgerteis
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

oa_search_sources

Read-onlyIdempotent

Search OpenAlex for journals, repositories, and conferences by name; filter by type and page through source results returned in a unified envelope.

Instructions

Search OpenAlex for sources: journals, repositories, conferences. Returns the unified envelope (record_type source).

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

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 / SourceSearchInput / 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 / SourceSearchInput / properties / query / maxLength
      Added value: +2000
  3. First observedv1.1.0

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is fully covered. The description adds one useful behavioral detail, the unified envelope with record_type 'source', but says nothing about pagination, cost, or empty-result behavior beyond what the per_page schema note carries.

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?

Two compact sentences, resource and subtypes front-loaded, with the return-envelope note second. Nothing wasted.

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?

An output schema exists, so return values need no explanation, and the read-only nature is covered by annotations. However, for a search tool with sibling search variants, the absence of routing guidance leaves a real gap for an agent choosing among the oa_search_* family.

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 adds no meaning about query, type, page, or per_page; type values and the per_page cost rationale live entirely in the nested schema, and reported schema coverage is 0%, so the description does not compensate for that gap.

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?

Specific verb plus resource with the resource subtypes spelled out ('journals, repositories, conferences'), which makes it distinguishable from oa_search_works/authors/institutions by entity type. It does not name a sibling explicitly, so it stops short of a 5.

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 when-to-use or when-not-to-use guidance, and no mention of alternatives such as oa_search_works when the entity is a work rather than a source. Usage is only implied by the phrase 'Search OpenAlex for sources'.

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