Skip to main content
Glama

Zotero List Libraries

zotero_list_libraries

Lists personal, group, and local RSS libraries with item counts so you can find the ID needed to switch libraries.

Instructions

List the libraries you can switch to: the personal library, group libraries (with group IDs) and, in local mode, RSS feeds, each with its item count. Use it to get an ID for zotero_switch_library. The active library is not marked.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

No annotations exist, so the description carries the full burden, and it delivers meaningful behavioral context: results are scoped to libraries you can switch to, group entries carry IDs, RSS feeds appear only in local mode, and the active library is explicitly not marked. That last caveat is genuinely useful because it warns the agent it cannot infer the current library from the output. It doesn't mention caching, permissions, or ordering, keeping it out of 5 territory.

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 short sentences, each carrying distinct information: what is listed, what it's for, and the active-library caveat. No filler and the content is front-loaded in the first clause.

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 does the work of sketching the return value (libraries with IDs and item counts) and flags the local-mode variation. For a zero-parameter read tool this is close to complete, though the agent must still infer the return shape and ordering at call time.

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?

The tool takes zero parameters, so there is no parameter meaning for the description to add; baseline for a parameterless tool is a 4.

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 and resource ("List the libraries") and enumerates exactly what is returned: personal library, group libraries with group IDs, and RSS feeds in local mode. An agent can distinguish this from zotero_switch_library or zotero_get_collections without opening any schema.

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?

Explicitly names the downstream use case: "Use it to get an ID for zotero_switch_library," which tells the agent this is the discovery step preceding a switch. It gives no exclusions or when-not-to-use conditions, and doesn't say whether it is needed before other library-scoped calls, so it stops short of a 5.

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