Skip to main content
Glama

Browse collections

browse_collections
Read-onlyIdempotent

List the collections plus Singles, each with the number of works it holds. Ask for one by name to get its works in full. Each collection includes its curatorial capsule alongside the works it contains.

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

Input Schema

NameRequiredDescriptionDefault
collectionNoOmit to list them all

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 readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is clear. The description usefully adds that results include work counts and curatorial capsules, and that named collections return full works, going beyond the annotations without contradicting them.

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 with no wasted language. The core list behavior and the optional detail mode are front-loaded, followed by useful return-content context.

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

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple read-only tool with one optional parameter, rich annotations, and no output schema, the description supplies enough about both list and detail behavior, including counts and curatorial capsules.

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?

Schema coverage is 100%, so the parameter is already documented, but the description adds meaning by explaining that supplying a collection name returns that collection's works in full rather than merely listing it.

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 states a specific verb and resource: list collections plus Singles with work counts, and optionally retrieve one collection's works in full. It is clear what the tool does, though it does not explicitly distinguish itself from siblings such as catalog_overview or search_artworks.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives clear usage for the optional parameter: omit it to list everything, or provide a collection name to get that collection's works in full. However, it does not state when to choose this tool over sibling browsing or search tools.

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