Skip to main content
Glama

List collections

list_collections
Read-onlyIdempotent

The collections in this server with document counts, the shelves within each, and the kinds of item (documents, images, film, audio). Use to see what the archive holds, or for the exact values the collection, sub_collection and media_type filters on search_records take.

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 observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, closed-world and non-destructive, so the safety profile is covered. The description adds valuable behavior beyond that by specifying the shape of the returned data (counts, nested shelves, item-kind taxonomy), which matters because no output schema exists. It does not mention ordering, size limits, or whether counts are live.

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?

Two sentences, both load-bearing, with the payload contents stated first and the motivating use case second. The opening sentence is a fragment lacking a head verb ('The collections in this server with...'), which costs a little immediate clarity but no words are wasted.

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 zero-parameter, read-only listing tool with no output schema, the definition covers both what comes back and why an agent would call it. The only gap is operational detail such as result size or ordering, which is minor for an archive-scoped listing.

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?

This tool takes zero parameters, so there is nothing for the description to disambiguate — the baseline of 4 applies. Its mention of collection/sub_collection/media_type is about consuming the output as filter values on a sibling tool, useful context rather than parameter documentation.

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 a concrete resource and enumerates exactly what it returns: collections, document counts, sub-collections ('shelves'), and item kinds (documents, images, film, audio). It is clearly distinguishable from search_records, but it is written as a noun phrase without a leading verb and does not differentiate itself from the counts-oriented archive_stats sibling.

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 two explicit use cases — seeing what the archive holds, and obtaining the exact legal values for the collection, sub_collection and media_type filters on search_records — which is a genuinely actionable call-to-use. It stops short of stating when NOT to use it or how it relates to archive_stats for count-based questions.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources