Skip to main content
Glama
ramiramirez-nl

doaj-discovery-mcp

by ramiramirez-nl
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Search DOAJ journals

search_doaj_journals
Read-onlyIdempotent

Search DOAJ-indexed journals using keywords and filter by country, language, license, or no-APC-only to identify open-access venues.

Instructions

Find DOAJ-indexed journals using lexical relevance and metadata preferences.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum number of results to return (1-25). Defaults to 10.
queryYesSearch text: keywords, a topic, or a short phrase (e.g. "diamond open access economics"). Longer text is automatically broadened if a narrow match returns nothing.
strictNoIf true, require every query term to match (AND) instead of relaxing to a broader OR match when the strict search returns nothing. Use for a well-defined, narrow query.
countryNoPublisher country as a name, e.g. "Turkey" or "Brazil" (not an ISO code). Narrows results to that country when recognized; otherwise only affects ranking.
licenseNoLicense substring to filter by, e.g. "CC BY" or "CC BY-NC".
languageNoJournal language as a name, e.g. "English" or "Turkish" (not an ISO code). Narrows results to that language when recognized; otherwise only affects ranking.
noApcOnlyNoIf true, only return journals with no article processing charge (diamond/no-fee open access).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0-beta.1

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint false. The description does not contradict these and adds useful context about lexical relevance and metadata filtering. No side effects or destructive behavior are implied.

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 a single concise sentence with no redundant wording. It conveys the essential purpose efficiently.

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?

The description is complete enough for a simple search tool with well-documented parameters and no output schema. It clearly indicates what is found, though it does not spell out exact return fields or explicitly contrast with article-level search.

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 coverage is 100% with rich parameter descriptions explaining behavior such as country/language fallback ranking and strict OR/AND matching. The one-sentence tool description adds little beyond the schema, so the baseline of 3 is appropriate.

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 clearly states the tool's action ('Find'), the resource ('DOAJ-indexed journals'), and the method ('using lexical relevance and metadata preferences'). This distinguishes it from sibling tools that search articles or focus on diamond OA journals.

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 does not explicitly say when to use this tool versus alternatives such as search_doaj_articles or find_diamond_oa_journals. The purpose is clear, but there is no direct guidance on selection criteria among the sibling tools.

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