Skip to main content
Glama
Sign In

Openaire

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Openaire Search Publications

openaire_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.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "machine learning cancer detection",
      "open_access": true
    },
    "name": "openaire_search_publications"
  }
}

Input 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

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. Added

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, open-world behavior, so the burden is lower. The description adds genuinely useful behavioral context beyond them: the index is an aggregated EU open-science corpus with stated funder coverage, which tells an agent what recall to expect. It says nothing about result ordering, deduplication, or rate limits.

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?

Dense and mostly front-loaded, with quoted user phrasings that aid intent matching. However, the actual verb+resource statement is buried after four example strings, which pushes the core purpose to the middle of the sentence.

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?

With an output schema present and full parameter documentation, the description only needs to establish scope, source, and use case — all of which it does. A note on corpus breadth or expected result volume would close the remaining gap for a paginated search tool.

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% and every parameter already carries a description, including funder short-name examples (EC, NIH, NSF, WT) and the ISO country code format. The description's "filter by funder, country, year range, open-access status" only restates the schema, so baseline 3 applies.

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?

States a specific verb and resource: "search scholarly publications (articles, preprints, theses, books) via OpenAIRE," and names the aggregator's provenance (EU open-science, EC/NIH/NSF/Wellcome coverage). The resource enumeration cleanly separates it from sibling tools that search datasets or projects.

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?

"Use for academic literature search with funder/policy context" gives a clear usage condition, reinforced by quoted trigger phrasings. It does not state when to prefer a different tool or what falls outside scope (e.g., software or dataset search), so it stops short of full routing guidance.

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