Skip to main content
Glama

Academic Research Search

search_arxiv

Search arXiv preprint server for scientific papers. Best for CS, physics, math, and AI research.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qYesSearch query (e.g. "transformer architecture", "quantum computing")
limitNoNumber of results (max 20, default 10)
categoryNoarXiv category: cs, physics, math, q-bio, stat, econ

TDQS

A3.7/5.0
Behavior2/5

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

No annotations are provided, so the description carries full responsibility. It only states the tool's core function without mentioning behavioral traits such as authentication requirements, rate limits, error handling, or result behavior (e.g., sorting, pagination). The agent gains little insight beyond the basic operation.

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?

The description is concise with two sentences, no redundancy. The first sentence captures the core purpose, and the second sentence adds domain context. Every word contributes meaning.

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?

For a search tool without an output schema, the description is minimally adequate. It covers the tool's domain and basic function but lacks details on result format, sorting, or expected response structure, which could hinder an agent from correctly interpreting output.

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 baseline is 3. The description adds no parameter-specific information beyond what the schema already provides. It does not elaborate on how to use the parameters effectively (e.g., query syntax, limit constraints).

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 clearly states the verb 'Search' and the resource 'arXiv preprint server for scientific papers'. It also specifies relevant fields (CS, physics, math, AI), which distinguishes it from siblings like search_pubmed (medical) and get_citations (citation retrieval).

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?

The description provides a clear context for when to use this tool ('Best for CS, physics, math, and AI research'). It implicitly suggests that other tools (search_pubmed) are better for medical literature, but no explicit when-not-to-use or alternatives are given.

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.

TDQS

A3.6/5.0
Disambiguation4/5

Each tool targets a distinct database or function (citations, arXiv, PubMed). However, get_citations can also search by topic, which might overlap with search_arxiv or search_pubmed in intent, though results differ.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern with lowercase and underscores: get_citations, search_arxiv, search_pubmed.

Tool Count4/5

Three tools is a minimal but reasonable set for an academic search server. It covers major repositories and citation lookup, but leaves room for more specialized searches.

Completeness3/5

The server covers arXiv, PubMed, and Crossref citations, but lacks other major databases (e.g., Google Scholar, IEEE Xplore) and full-text retrieval, which are notable gaps for a comprehensive academic search tool.

Resources