Skip to main content
Glama

Search Swiss academic libraries (swisscovery)

search_library_catalogue
Read-only

Search the swisscovery union catalogue of Swiss academic libraries by keywords, title, author, subject, or ISBN to retrieve bibliographic records and links for checking holdings and availability.

Instructions

Search the swisscovery union catalogue of Swiss academic libraries by keywords, title, author, subject or ISBN (fields are combined with AND). Returns bibliographic records (title, creators, publisher, year, ISBN, subjects, online links) and a swisscovery link to check holdings/availability. Example: {author: 'Spyri', title: 'Heidi'}, {subject: 'Gletscher', keywords: 'Klimawandel'}.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search_library_catalogue"
  }
}

Input Schema

NameRequiredDescriptionDefault
isbnNo
limitNo
titleNo
authorNo
offsetNo
subjectNo
keywordsNoFree-text keywords (all fields)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.3

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint and openWorldHint, so safety and network scope are covered. The description adds genuinely useful behaviour — that records include online links and that holdings/availability must be checked via the returned swisscovery link rather than being returned directly — but says nothing about result limits, pagination, or empty-result behaviour.

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 sentences, front-loaded with the resource and access points, then return contents, then worked examples. Every element earns its place and nothing is padded.

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?

With no output schema, the description correctly documents the returned record fields and the follow-up holdings link, which is the key thing an agent needs. Minor gap: it does not mention the result cap (limit max 50) or how to page through large result sets via offset.

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?

Schema coverage is only 14%, so the description must carry the load, and it does for the five search fields by naming them and stating they are AND-combined — a real semantic addition beyond the bare schema. The limit/offset parameters are left unexplained, though their meaning is largely self-evident.

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 (Search) plus the exact resource (swisscovery union catalogue of Swiss academic libraries) and the supported access points. No sibling tool searches library catalogues, and the title/description make the scope unmistakable.

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?

Explains that fields are combined with AND and gives two concrete example query shapes, which tells the agent how to compose a search. It does not state when to prefer this over other search tools or what to do when no records are found, so it stops short of explicit alternatives/exclusions.

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