exlibris_primo_mcp_search_catalog

1 MCP server offers this tool

What it usually takes

  • availability – in 1 of 1
  • collection – in 1 of 1
  • field – in 1 of 1
  • full_text_only – in 1 of 1
  • language – in 1 of 1
  • library – in 1 of 1
  • max_results – in 1 of 1
  • offset – in 1 of 1
  • precision – in 1 of 1
  • query – in 1 of 1
  • resource_type – in 1 of 1
  • return_facets – in 1 of 1

No server marks it as only reading: treat it as able to change data.

From each publisher's own tool list. We never call a tool.

Servers

ServerInputsRead-only?
ExLibris Primo MCP demo co.huggingface.geraldine/exlibris-primo-mcp Search an Ex Libris Primo discovery layer (library catalogue and discovery index). Primo is institution-scoped. The API key and the gateway come from the X-Primo-* request headers listed in this tool's meta.headers, falling back to what the deployment configured; the view can also be set per call below. Returns: {"source": "primo", "command": "search_catalog", "total_found": int, "returned": int, "offset": int, "query_used": str, "vid": str, "results": [{"source": "primo", "record_id": str, "title": str, "authors": [str], "year": int | null, "publisher": str | null, "doc_type": str | null, "record_url": str | null}], "error": str | null}availability,collection,field,full_text_only,language,library,max_results,offset,precision,query,resource_type,return_facets,scope,sort,tab,vid,year_from,year_toNot stated