Skip to main content
Glama

list_collections

Read-onlyIdempotent

Lists existing Kavita collection and library names so you can reuse them and avoid near-duplicates before adding a document.

Instructions

The user's collection names and library names, to reuse instead of inventing near-duplicates before add_document.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered by structured data. The description adds the practical motivation (dedupe before writing) but says nothing about return shape, whether IDs or only display names come back, or how transient/stale the listing is.

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?

One short sentence, front-loaded with what the tool returns and followed by the reason to call it. No filler or redundancy. The opening noun phrase is slightly elliptical ('The user's collection names...' rather than 'Lists...'), which costs a point.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/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 is the only source of information about return values, and it only loosely implies a list of names without saying whether identifiers, counts, or library-vs-collection grouping are included. For a trivial no-param listing tool this is close to adequate, but the return contract remains underspecified.

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

Parameters3/5

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

The tool takes zero parameters, so the schema has nothing to document and there is no parameter semantics to clarify. Baseline for a no-param tool is 4, but here the description's only non-name content is usage motivation rather than anything about how the call is shaped, so it lands just below that.

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 names the resource precisely ('the user's collection names and library names'), which tells an agent exactly what this tool surfaces and implicitly distinguishes it from list_library by covering both collections and libraries. The verb is absent, but the tool name supplies 'list' unambiguously.

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 gives an explicit trigger and a named downstream consumer: call this before add_document so existing names can be reused instead of inventing near-duplicates. That is concrete when-to-use guidance. It stops short of stating exclusions or what to do if no matching name exists.

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