Skip to main content
Glama

search_all

Aggregated search across arXiv, Semantic Scholar, OpenAlex and Yongleji at once. Fans out concurrently, de-duplicates the same work across corpora (by DOI or title) and re-ranks with Reciprocal Rank Fusion, so papers found by several sources rank highest. Each hit lists which sources found it and an ids map ({source: id}) you can pass to get_paper / read_paper / the citation tools. Prefer this over search_papers for a broad lookup.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "search_all"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYes
sourcesNoarxiv,semanticscholar,openalex,yongleji
per_sourceNo
max_resultsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / sources / default
      Previous value: -"arxiv,semanticscholar,openalex"New value: +"arxiv,semanticscholar,openalex,yongleji"
  2. First observed

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses concurrent fan-out, de-duplication by DOI or title, and Reciprocal Rank Fusion re-ranking with the resulting rank behavior. It omits operational traits such as latency, rate limits, or what happens when one corpus fails, which keeps it below a 5.

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?

Three tight sentences, front-loaded with what the tool is and the corpora it covers, followed by mechanism and then return shape. The mention of the `ids` map is not filler because there is no output schema to carry that information.

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?

Return-shape coverage is good for a tool with no output schema, and the mechanism (dedup, RRF) is well explained. However, for a 4-parameter tool with zero schema descriptions and no annotations, leaving three parameters undocumented makes the definition incomplete for correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must explain the four parameters, and it largely does not. It alludes to `sources` only as a return field and never states the comma-separated string format or that it filters the corpora; `per_source` and `max_results` (including the meaning of per_source=0) are entirely unaddressed.

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?

The description names a specific verb (aggregated search) and enumerates the exact corpora it spans (arXiv, Semantic Scholar, OpenAlex, Yongleji), which no sibling does. It also explicitly distinguishes itself from search_papers, so an agent can route without opening either 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?

"Prefer this over search_papers for a broad lookup" gives an explicit alternative and the condition that selects it. It stops short of stating when NOT to use it (e.g., when a single corpus or a specialized index like search_medical is the target), so routing is clear but not fully bounded.

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.