apibase

DOAJ — Search Open Access Journals

doaj.journals.search

Read-onlyIdempotent

Search the Directory of Open Access Journals (DOAJ) for peer-reviewed, fully open access journals. DOAJ indexes 20,000+ journals in 80+ languages from 129 countries — all free to read, CC-licensed, and vetted for quality. Query by topic, ISSN, publisher, or DOAJ query syntax. Returns title, ISSN, publisher, country, subject classification, license type, APC cost, preservation services (CLOCKSS, Portico, LOCKSS), and OA start year. Useful for finding publishing venues, checking journal legitimacy, and academic research.

Input Schema

TableJSON Schema

Name	Required	Description
`page`	No	Result page number (1-based). Default: 1.
`sort`	No	Sort order for results. Examples: "title:asc", "issn:desc". Default: relevance.
`query`	Yes	Search query for journals (e.g. "ecology", "ISSN:1234-5678", "publisher:Elsevier"). Supports DOAJ query syntax.
`page_size`	No	Number of journals per page (1–50). Default: 10.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`error`	No	Present only when the call failed. Includes error code, message, request_id, and any provider-specific extras.
`result`	No	Tool response payload. Shape varies per tool — consult the tool description and inputSchema. May be an object, array, string, or number depending on the upstream provider response.

Schema Changelog

Changes observed during successful MCP inspections.

First observedSep 22, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already establish read-only, idempotent, open-world behavior, so the description correctly focuses on adding context: it reveals the scope of DOAJ's coverage, the quality filter, and the exact fields returned (APC cost, preservation services, OA start year). This goes beyond the annotations without contradicting them.

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?

The description is dense but purposeful: the first sentence states the action, the second adds scale and quality context, and the final sentence lists useful application scenarios. Minor redundancy exists ('free to read' and 'OA' overlap), but overall every sentence contributes information an agent would need.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Combined with the 100% schema coverage, the deterministic annotations, and an output schema, this description is nearly complete for a search tool. It explains what to search, how to structure queries, and what fields come back. The only small gap is not explicitly routing to sibling tools like doaj.articles.search for article-level searches.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3. The description adds genuine value by providing real query syntax examples ('ISSN:1234-5678', 'publisher:Elsevier') and mentioning DOAJ query syntax support, which helps an agent construct valid queries beyond the bare schema property descriptions.

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

Purpose5/5

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

The description uses a specific verb ('Search') and names the exact resource (Directory of Open Access Journals). It clearly distinguishes this tool from siblings like doaj.articles.search and doaj.journals.detail by focusing on journal-level search and explicitly enumerating the returned journal metadata.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives concrete query examples (topic, ISSN, publisher) and states use cases like finding publishing venues and checking journal legitimacy. It does not explicitly compare to doaj.articles.search or doaj.journals.detail, but the journal-specific focus provides clear context for when to use this tool.

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

All apibase tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.