Skip to main content
Glama
ramiramirez-nl

doaj-discovery-mcp

by ramiramirez-nl
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Find diamond OA journals

find_diamond_oa_journals
Read-onlyIdempotent

Search the DOAJ for diamond open-access journals with no publication fees. Enter keywords to find free-to-publish journals for your research.

Instructions

Find no-fee or diamond open-access DOAJ journals.

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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0-beta.1

TDQS

A4.3/5.0
Behavior4/5

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

The annotations (readOnlyHint, openWorldHint, idempotentHint, destructiveHint) already fully disclose the behavioral profile. The description is consistent with these annotations and adds no contradictory or additional side-effect information, but also does not go beyond them.

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 that communicates the essential purpose without any fluff or redundant information.

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 clear on its own, but given the presence of sibling tools like search_doaj_journals, it could be more complete by noting that this tool is a specialized subset (filtering for no-fee or diamond OA). Still, the core context is adequate.

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

Parameters5/5

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

All three parameters (query, limit, strict) are fully described in the schema: types, defaults, and purpose. The strict parameter's behavior (AND vs OR) is explicitly explained, and limit has clear bounds. Schema description coverage is 100%.

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 verb 'Find' and the specific resource: no-fee or diamond open-access DOAJ journals. It is unambiguous and directly conveys the tool's purpose.

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

Usage Guidelines3/5

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

The description does not explicitly indicate when to use this tool versus the sibling search_doaj_journals or other related tools. While the purpose is specific, guidance on when to prefer this over a general search is missing.

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