Skip to main content
Glama

arxiv_search

Read-onlyIdempotent

Search arXiv for scientific preprints by keyword, title, or author and return up to 20 matching papers.

Instructions

Search arXiv for scientific preprints by keyword, title, or author.

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": "arxiv_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesSearch term or arXiv query.
max_resultsNoMax papers to return (default 5, max 20).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.11

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and openWorldHint=true, so the safety and external-reach profile is covered. The description adds only the accepted query modes, and says nothing about result ordering, relevance ranking, or the fact that returned entries are metadata-only (no full text).

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?

A single front-loaded sentence with no filler. The resource, the verb, and the accepted query modes appear immediately.

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 two-parameter read-only search with 100% schema coverage and full annotations, the description plus structured data give an agent enough to call it correctly. It could be marginally richer by noting that results are preprints (not peer-reviewed publications) and the max of 20, but nothing essential is 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 coverage is 100%, with the query and max_results (default 5, max 20) parameters fully documented in the schema. The description's "by keyword, title, or author" adds a small hint that the query string can target different fields, but doesn't give query syntax or field-prefix details. Baseline 3 applies when the schema carries the load.

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?

States a specific verb and resource ("Search arXiv for scientific preprints") and names the accepted query modes. No sibling in the tool list covers arXiv, so differentiation is largely unnecessary; the only gap versus a 5 is that it doesn't distinguish this from generic scholarly search siblings such as openalex_search_works or crossref_search_works.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance on when to use this versus the many other scholarly search tools (openalex_search_works, dblp_search_publications, crossref_search_works), nor any note on when it is inappropriate. Usage is only implied by the verb "search".

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