Skip to main content
Glama

Zotero Switch Library

zotero_switch_library

Set the active Zotero library for all later tool calls in the session, choosing a user, group, or feeds library or reverting to the configured default.

Instructions

Set the library that every later tool call reads and writes, for the rest of the session. library_id: an ID from zotero_list_libraries ('user' or '0' for the personal library). library_type: 'group' (default), 'user', 'feeds', or 'default' to go back to the configured library (library_id is then ignored). Fails if the library is not accessible.

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": {
      "library_id": "<library_id>"
    },
    "name": "zotero_switch_library"
  }
}

Input Schema

NameRequiredDescriptionDefault
library_idYes
library_typeNogroup

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations, the description carries the full load and does well: it discloses that the setting is session-persistent, that the call fails when the library is inaccessible, and that library_id is silently ignored when library_type='default'. It stops short of saying whether a success response confirms the active library or whether authorization is needed for group writes.

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 tight paragraph: the session-wide effect leads, then parameter semantics follow. Every clause carries information an agent needs; no filler or restatement of the title.

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 session-state tool with no annotations and no output schema, the description covers purpose, parameters, defaults, precedence, and failure mode. Only the post-call feedback (whether the response echoes the newly active library) is unaddressed, which is a minor gap.

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

Parameters5/5

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

Schema description coverage is 0% and no enums are declared, yet the description supplies the meaning of both parameters: library_id accepts a value from zotero_list_libraries including the 'user'/'0' personal-library shorthand, and library_type takes 'group' (default), 'user', 'feeds', or 'default', plus the precedence rule that library_id is ignored for 'default'.

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 first sentence names a specific verb ('Set') and resource ('the library') and, crucially, states the scope of effect: every later tool call, for the rest of the session. That immediately distinguishes it from the sibling read/write tools like zotero_list_libraries or zotero_get_recent.

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?

It tells the agent where library IDs come from (zotero_list_libraries) and how to revert (library_type 'default'), which covers the main usage decisions. It doesn't state an explicit ordering rule such as 'call this before any item tool' or what happens to the previously selected library, so the guidance is clear but not exhaustive.

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