Skip to main content
Glama

Literature Search - scholarly papers via OpenAlex + Crossref

literature_search
Read-onlyIdempotent

Search 250M+ scholarly works (journals, preprints, conferences, books) from OpenAlex, with Crossref fallback: title, authors, year, venue, DOI, citation count, open-access PDF link and abstract. Filter by year, open access only, sort by relevance, citations or newest. ~1-2 s. Free: 25 calls/day per IP. Paid: $0.004 per call via x402 at https://radarbg.com/x402/literature-search.

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": {
      "sort": "citations",
      "query": "large language models radiology",
      "fromYear": 2023,
      "maxItems": 5
    },
    "name": "literature_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
sortNorelevance, citations or newestrelevance
queryYesTopic or keywords, e.g. large language models radiology
sourceNoopenalex (default, falls back to crossref) or crossrefopenalex
toYearNoPublished in or before this year
fromYearNoPublished in or after this year
maxItemsNoMax results (1-50)
openAccessOnlyNoOnly works with a free full text (OpenAlex)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already declare readOnly/openWorld/idempotent, and the description adds substantial context beyond them: expected latency (~1-2 s), the free quota (25 calls/day per IP), the paid path at $0.004/call via x402 with an endpoint URL, and the OpenAlex->Crossref fallback. These cost and rate-limit details are exactly what an agent needs before invoking.

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?

Four sentences, each doing work: corpus plus return fields first, then filtering/sorting, then latency, then pricing. No filler or repetition, and the core purpose is front-loaded.

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

Completeness5/5

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

With 7 parameters and no output schema, the description compensates by listing the returned fields and the corpus size, and it covers cost, rate limits, latency, and fallback behavior. Nothing an agent needs to call this correctly appears to be missing.

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%, with enum values and defaults already documented for sort, source, and openAccessOnly, so the schema carries the parameter semantics. The description only restates the filter and sort options at a high level without adding syntax or edge-case meaning, which matches the baseline 3 for a fully documented 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?

States a specific verb and resource ('Search 250M+ scholarly works ... from OpenAlex, with Crossref fallback') and enumerates the returned fields (title, authors, year, venue, DOI, citations, OA PDF, abstract). No sibling tool covers scholarly literature, so the agent can distinguish it from airport_report, clinical_trials, web_read, etc. without opening the schema.

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?

Gives clear operating context: filters by year, open-access-only, and sort by relevance/citations/newest, plus the conditional behavior that OpenAlex is the default and Crossref is the fallback. It does not state when NOT to use it or name an alternative tool, but no sibling offers overlapping capability, so this is close to sufficient.

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