Skip to main content
Glama

Doaj

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Search Articles

search_articles
Read-onlyIdempotent

Search peer-reviewed open-access articles. Supports Lucene-style field queries (title:climate, abstract:"machine learning", year:2023, author:Doe).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNo1-based page (default 1)
sortNoSort field:dir, e.g. "created_date:desc"
queryYesFree-text or Lucene-style query
page_sizeNo1-100 (default 10)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoCurrent page
totalNoTotal results
resultsNoArray of article results
pageSizeNoItems per page

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "query": "title:climate change"
+  },
+  {
+    "page": 1,
+    "page_size": 20,
+    "query": "abstract:\"machine learning\" AND year:2023",
+    "sort": "created_date:desc"
+  }
+]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "page": {
+      "description": "Current page",
+      "type": "number"
+    },
+    "pageSize": {
+      "description": "Items per page",
+      "type": "number"
+    },
+    "results": {
+      "description": "Array of article results",
+      "items": {
+        "properties": {
+          "abstract": {
+            "description": "Article abstract",
+            "type": "string"
+          },
+          "author": {
+            "description": "List of authors",
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          },
+          "created_date": {
+            "description": "Creation date",
+            "type": "string"
+          },
+          "id": {
+            "description": "DOAJ article ID",
+            "type": "string"
+          },
+          "journal": {
+            "description": "Journal title",
+            "type": "string"
+          },
+          "title": {
+            "description": "Article title",
+            "type": "string"
+          },
+          "year": {
+            "description": "Publication year",
+            "type": "number"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "total": {
+      "description": "Total results",
+      "type": "number"
+    }
+  },
+  "type": "object"
+}
  2. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already indicate it is read-only and idempotent. The description adds behavioral context by specifying the Lucene query syntax support and the article source (peer-reviewed open-access), which goes beyond the 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 two sentences, each serving a distinct purpose: stating the tool's function and specifying query syntax. It is front-loaded with the core purpose and contains no 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?

Given the presence of an output schema and comprehensive annotations, the description adequately covers the tool's purpose and query capabilities. It could be improved by mentioning result limitations or pagination behavior, but these are covered by the schema.

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?

With 100% schema coverage, the schema already describes each parameter. The description adds value by providing concrete examples of Lucene-style queries ('title:climate', 'abstract:"machine learning"'), enhancing understanding of the 'query' parameter beyond its schema description.

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 identifies the tool as searching peer-reviewed open-access articles, with explicit support for Lucene-style field queries. This verb+resource combination is specific and distinguishes it from sibling tools like search_journals or deep_research.

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 states what the tool does but provides no guidance on when to use it versus sibling tools (e.g., deep_research, search_journals). There is no mention of appropriate contexts or exclusions.

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

All Doaj toolsInspect
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.

Resources