Skip to main content
Glama
malkreide

swiss-academic-libraries-mcp

by malkreide

search_preprints

Read-onlyIdempotent

Search for preprints on arXiv to find open access versions of scholarly articles across natural sciences, computer science, and mathematics.

Instructions

Durchsucht Preprints auf arXiv (Naturwissenschaften, Informatik, Mathematik u.a.).

Beantwortet «gibt es davon eine frühe/offene Fassung?». Die Anfrage wird automatisch als exakte Phrase gesucht — du musst keine arXiv-Syntax kennen (arXiv würde Leerzeichen sonst als OR interpretieren). Wo arXiv eine verknüpfte Journal-DOI führt, ist sie im Feld doi enthalten und lässt sich mit resolve_doi zur peer-reviewten Fassung auflösen — die sich wiederum in swisscovery gegen den Schweizer Bestand prüfen lässt.

Args: params (SearchPreprintsInput): query, category (optional, z.B. 'cs.CL'), limit, response_format.

Returns: str: Trefferliste mit arXiv-ID, Kategorie, Datum, ggf. Journal-DOI und Abstract, oder ein Hinweis bei null Treffern.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
paramsYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

Annotations already declare safe read-only, idempotent behavior. The description adds that queries are auto-treated as exact phrases, details return format, and explains DOI resolution, providing useful context beyond annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is informative and well-structured, starting with purpose, then usage context, then parameter details. It is somewhat lengthy but each sentence adds value, making it efficient.

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?

Given the tool's complexity (nested input, output schema, related tools), the description covers purpose, usage, behavior, and parameter nuances. It references sibling tools in workflow, making it nearly complete.

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

Parameters4/5

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

Despite schema descriptions present for all parameters, the tool description adds significant value for the query parameter (auto-phrasing, arXiv syntax handling). Schema coverage is indicated as 0% but descriptions exist; the description compensates.

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?

The description clearly states the tool searches arXiv preprints in sciences and answers if an early/open version exists. It does not explicitly differentiate from sibling tools like search_publications, but mentions related tools and workflow.

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?

The description implies usage for finding preprints and explains query handling (auto-phrasing). It mentions using resolve_doi and swisscovery for follow-up, but lacks explicit when-to-use vs. alternatives or exclusion criteria.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/malkreide/swiss-academic-libraries-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server