Skip to main content
Glama

Openaire

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Search Publications

search_publications
Read-onlyIdempotent

"Find papers about [topic]" / "search EU / open-access research on [X]" / "publications by [funder]" / "academic articles on [Y]" — search scholarly publications (articles, preprints, theses, books) via OpenAIRE (the EU's open-science aggregator; covers EC / NIH / NSF / Wellcome Trust funded research). Filter by funder, country, year range, open-access status. Use for academic literature search with funder/policy context.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNo1-based page (default 1)
sizeNoPage size, 1-100 (default 20)
queryYesFree-text query (matches title/abstract/keywords)
funderNoFunder short name — e.g. "EC", "NIH", "NSF", "WT"
countryNoCountry code — ISO 3166-1 alpha-2
to_yearNoLatest publication year (YYYY)
from_yearNoEarliest publication year (YYYY)
open_accessNoRestrict to open-access publications

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageYesCurrent page number (1-based)
countYesNumber of results in this response
queryYesThe search query that was executed
totalYesTotal number of matching publications
resultsYesArray of publication objects
page_sizeYesNumber of results per page

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "open_access": true,
+    "query": "machine learning cancer detection"
+  },
+  {
+    "country": "DE",
+    "from_year": "2020",
+    "funder": "EC",
+    "query": "climate change impact",
+    "to_year": "2023"
+  }
+]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "count": {
+      "description": "Number of results in this response",
+      "type": "number"
+    },
+    "page": {
+      "description": "Current page number (1-based)",
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "page_size": {
+      "description": "Number of results per page",
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "query": {
+      "description": "The search query that was executed",
+      "type": "string"
+    },
+    "results": {
+      "description": "Array of publication objects",
+      "items": {
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "total": {
+      "description": "Total number of matching publications",
+      "type": [
+        "number",
+        "null"
+      ]
+    }
+  },
+  "required": [
+    "query",
+    "total",
+    "page",
+    "page_size",
+    "count",
+    "results"
+  ],
+  "type": "object"
+}
  2. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive. Description adds valuable context: uses OpenAIRE, covers specific funders (EC, NIH, NSF, Wellcome Trust). No contradiction.

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?

Single well-structured sentence, front-loaded with action. Slightly dense but concise; examples integrated naturally.

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?

For a search tool with output schema, description covers key aspects: purpose, source, filters. Could mention result ordering or pagination, but not essential given schema.

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 detailed descriptions. Description reinforces parameter usage through examples but does not add novel semantics beyond the schema.

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?

Description clearly states it searches scholarly publications via OpenAIRE, with filters for funder, country, year, and open-access. Examples and specific verb 'search' differentiate it from sibling tools like search_datasets or search_software.

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?

Provides example queries and context for use (e.g., 'search EU / open-access research'). Implicitly guides when to use via mention of funder/policy context, but lacks explicit 'when not to use' or alternative references.

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

All Openaire 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