Skip to main content
Glama

Open data: clinical trials, EU tenders, companies, fuel prices

Scholarly Paper Search (OpenAlex): DOI, year, venue, citations, open-access link

scholarly-search
Read-onlyIdempotent

Search the OpenAlex index of scholarly works by keyword, year range and open-access status, and get each paper's title, DOI, year, venue, type, citation count and open-access link. Read from api.openalex.org when called. Each result: openalex_id, title, doi, year, publication_date, venue, type, cited_by_count, is_open_access, oa_status, open_access_url, language. Needs a RapidAPI key for this API (https://rapidapi.com/IanGregory/api/clinical-trials-eu-tenders-open-data-api), sent as the X-RapidAPI-Key header; the listing has a free plan.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "scholarly-search"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoAt most this many results (default 100).
queryNoKeywords to search for in titles, abstracts and full text. Example: "graph neural networks".
year_toNoLast publication year to include. Example: 2026.
oa_statusNoKeep only works with this open-access status (empty: all works). Example: "green".
year_fromNoFirst publication year to include. Example: 2020.

Output Schema

NameRequiredDescriptionDefault
countYeshow many results came back
itemsYesthe results, one object each
partialNosome of the source's requests failed: the results are incomplete
productNo
sourcesNowhere the data came from: each source's name, licence and the attribution to show with it
fetched_atNowhen the source was read (Unix seconds)
truncated_fromNothe answer was cut to fit: this many results came back in all

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedOutput schema / properties / sources
      Added value: +{
      +  "description": "where the data came from: each source's name, licence and the attribution to show with it",
      +  "items": {
      +    "type": "object"
      +  },
      +  "type": "array"
      +}
  2. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "count": {
      +      "description": "how many results came back",
      +      "type": "integer"
      +    },
      +    "fetched_at": {
      +      "description": "when the source was read (Unix seconds)",
      +      "type": "integer"
      +    },
      +    "items": {
      +      "description": "the results, one object each",
      +      "items": {
      +        "properties": {
      +          "cited_by_count": {
      +            "description": "cited_by_count (integer)"
      +          },
      +          "doi": {
      +            "description": "doi (text)"
      +          },
      +          "is_open_access": {
      +            "description": "is_open_access (bool)"
      +          },
      +          "language": {
      +            "description": "language (text)"
      +          },
      +          "oa_status": {
      +            "description": "oa_status (text)"
      +          },
      +          "open_access_url": {
      +            "description": "open_access_url (url)"
      +          },
      +          "openalex_id": {
      +            "description": "openalex_id (url)"
      +          },
      +          "publication_date": {
      +            "description": "publication_date (date)"
      +          },
      +          "title": {
      +            "description": "title (text)"
      +          },
      +          "type": {
      +            "description": "type (text)"
      +          },
      +          "venue": {
      +            "description": "venue (text)"
      +          },
      +          "year": {
      +            "description": "year (integer)"
      +          }
      +        },
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "partial": {
      +      "description": "some of the source's requests failed: the results are incomplete",
      +      "type": "boolean"
      +    },
      +    "product": {
      +      "type": "string"
      +    },
      +    "truncated_from": {
      +      "description": "the answer was cut to fit: this many results came back in all",
      +      "type": "integer"
      +    }
      +  },
      +  "required": [
      +    "count",
      +    "items"
      +  ],
      +  "type": "object"
      +}
  3. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Adds real context beyond the annotations: the upstream endpoint is api.openalex.org, a RapidAPI key is required, it is sent as the X-RapidAPI-Key header, and a free plan exists. That auth disclosure is exactly what annotations cannot convey. Deduction because the supplied RapidAPI listing URL points at "clinical-trials-eu-tenders-open-data-api", which does not match this tool and could send an agent to provision the wrong key.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Purpose is front-loaded in the first clause, which is good, but the sentence enumerating all twelve result fields duplicates the output schema that already exists. The stray mismatched RapidAPI link also costs space and adds noise rather than value.

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 read-only, five-parameter search with an output schema, the critical missing pieces were the upstream source and authentication, and both are covered. Return-value explanation is legitimately omitted elsewhere since the output schema carries it, though the duplicated field list and wrong API link slightly muddy the picture.

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 description coverage is 100%, so limit, query, year_from, year_to and oa_status are already documented with examples and an enum. The description only restates "keyword, year range and open-access status" without adding syntax, defaulting or interaction rules (e.g. how year_from/year_to combine).

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 ("Search") and resource ("the OpenAlex index of scholarly works") plus the filter dimensions and what comes back, so an agent knows exactly what it retrieves. No sibling tool covers scholarly literature, so the domain alone distinguishes it from app-store-search, clinical-trials-monitor and the rest.

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?

Implies the tool is for keyword/year/open-access literature lookup, but never says when to prefer it or when it is the wrong choice (e.g. author-only or citation-graph queries that OpenAlex supports differently). There are no exclusions or prerequisites beyond the auth note.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources