Skip to main content
Glama

List collections

list_collections
Read-only

Lists available model collections with purposes, tags, members, context limits, and rate limits so you can choose the right panel for a task before asking.

Instructions

The collections this Benchwarmers server offers: name, what each is for, tags, members, explorer seats, reply mode, and what the members handle together (smallest context window, shared capabilities, tightest rate limits). Pick by task before calling ask. A collection the user names may not be listed here: ask it anyway.

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

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered; the description adds real value by disclosing what the response actually contains, including the aggregate per-collection limits ('smallest context window, shared capabilities, tightest rate limits'). It also discloses the important caveat that the list may be incomplete relative to what the user names, which is behavioral context no annotation carries.

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 compact sentences, front-loaded with what is returned and followed by the call-to-action guidance. The parenthetical of aggregate traits ('smallest context window, shared capabilities, tightest rate limits') is dense and slightly opaque jargon, but every clause carries information.

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 description takes on the burden of describing the return shape and does so field by field. What remains unclear is the meaning of domain jargon like 'explorer seats' and 'reply mode', which an agent would have to guess at.

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 no parameters, so there is nothing for the description to disambiguate; baseline 4 applies. The description uses its space on return content instead of wasting words on inputs.

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 makes clear this returns the catalog of collections available on this server and enumerates the fields each entry carries (name, purpose, tags, members, explorer seats, reply mode, aggregate capabilities). It is clearly a read-only listing, distinguishable from ask/verdict. It stops just short of a crisp verb-led statement, opening with the noun phrase 'The collections this Benchwarmers server offers'.

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

Usage Guidelines5/5

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

It explicitly routes the agent: 'Pick by task before calling ask', naming the sibling and the ordering relationship. It also covers the negative case — 'A collection the user names may not be listed here: ask it anyway' — so the agent knows not to block on a missing entry.

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

Deploy Server

Other Tools