Skip to main content
Glama

List collections

list_collections
Read-onlyIdempotent

Research collections, one per project, ranked by research-item count and cited by the project page. Feed an id or code into search_research_items.collection.

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
limitNoDefault 50, max 200
offsetNo
keywordNoFilter on the collection title, project name or code; every word must match

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / keyword / description
      Previous value: -"Substring filter on the collection title, project name or code"New value: +"Filter on the collection title, project name or code; every word must match"
  2. Changed1 schema field changed
    • removedInput schema / $schema
      Removed value: -"https://json-schema.org/draft/2020-12/schema"
  3. Changed1 schema field changed
    • changedInput schema / properties / keyword / description
      Previous value: -"Substring filter on the collection title"New value: +"Substring filter on the collection title, project name or code"
  4. Changed1 schema field changed
    • removedInput schema / properties / limit / maximum
      Removed value: -9007199254740991
  5. Changed1 schema field changed
    • addedInput schema / properties / keyword / maxLength
      Added value: +1000
  6. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered elsewhere. The description adds genuine behavioral context beyond that: the ranking is by research-item count and each collection maps to one project. It does not mention page-size behavior or what happens when results exceed the limit, which an agent would want to know.

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 dense sentences with no filler, and the resource definition plus ordering is front-loaded before the chaining hint. It is very close to under-specified rather than concise, and the trailing project-page clause earns little for its ambiguity.

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 does need to convey the shape of the result, and it partially does (collections tied to projects, ordered by item count, carrying ids/codes). However, it omits pagination/truncation semantics for a paged list tool (default 50, max 200), leaving a real gap for correct invocation.

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

Parameters2/5

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

At 67% schema coverage, limit and keyword are already documented in the schema, while offset has no description anywhere. The description mentions "id or code" only as something consumed by another tool, adding no meaning about limit, offset, or keyword matching behavior, so it contributes essentially nothing over the structured fields.

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 the resource precisely: collections are "one per project, ranked by research-item count," which tells an agent exactly what entity set it is enumerating and how it is ordered. It stops short of a clean verb-first statement of purpose (that it lists/paginates collections) and the phrase "cited by the project page" is somewhat opaque, but the resource is still distinguishable from siblings like compare_collections or list_categories.

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?

The only guidance is "Feed an id or code into search_research_items.collection," which usefully names a downstream step but is a chaining hint rather than a when-to-use rule. There is no statement of when to call this instead of compare_collections or the other list_* tools, and no exclusion conditions are given.

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.