Skip to main content
Glama
Sign In
open-data-mcp

open-data-mcp

by markatdataandbeyond
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

dataandbeyond--scholar-search

Read-only

Search academic papers across Crossref, arXiv, and OpenAlex, ranked by relevance and citations, to find research sources for topics or keywords.

Instructions

Academic papers from Crossref and arXiv (and OpenAlex if OPENALEX_API_KEY is set), ranked by relevance and citations. Calls the official APIs directly.

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": "dataandbeyond--scholar-search"
  }
}

Input Schema

NameRequiredDescriptionDefault
queriesNoFree-text topics, titles or keywords. Example values: ["knowledge graph embedding"]
sourcesNoAny of: crossref, arxiv, openalex. OpenAlex is used when the Actor has the OPENALEX_API_KEY environment variable set. Example values: ["crossref","arxiv","openalex"]
fromYearNoOnly papers published this year or later.
waitSecsNoMax seconds (0–45, default 30) to cap the wait for the Actor run to reach terminal state. For long-running Actors the response returns at the cap with the current run status; follow `nextStep` to poll via get-actor-run. Set to 0 to fire-and-forget.
maxResultsPerQueryNoDeduplicated papers per query. Example values: 10

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, openWorldHint and destructiveHint=false, so safety is covered. The description adds useful context about which backends are queried, that OpenAlex depends on an environment variable, and that results are ranked by relevance and citations, but says nothing about latency, per-source failure modes, or result field coverage.

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?

Two short sentences, resource and sources front-loaded, conditional detail last. Nothing is padded or redundant.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description leaves the agent guessing about result shape (per-paper fields such as title, DOI, citation count, source label), deduplication across sources, and what the async waitSecs/nextStep polling flow yields. It covers the 'what' but not enough of the 'what comes back' for a multi-source aggregation 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 description coverage is 100%, so every parameter (queries, sources, fromYear, waitSecs, maxResultsPerQuery) is already documented in structured data. The description's only parameter-relevant content, the OpenAlex key condition, duplicates the `sources` schema description, so it adds no net meaning.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Names the concrete resource (academic papers) and the exact upstream sources (Crossref, arXiv, optionally OpenAlex), plus the ranking basis (relevance and citations). An agent can tell this is a scholarly literature search, though it never uses an explicit verb like 'search' and doesn't contrast itself with the sibling pubmed-search tool.

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?

Usage is only implied by the source list; there is no statement of when to choose this over dataandbeyond--pubmed-search or any other sibling. The conditional OpenAlex behavior hints at a prerequisite, but no exclusions or alternatives are spelled out.

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