Skip to main content
Glama

List the wellness music catalog

list_catalog

List all 9 albums and 27 wellness music tracks with prices ($5.99/track, $14.99/album) and per-track session evidence. No payment required.

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_catalog"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description must carry the whole burden, and it does disclose that the operation is free ('No payment required') and that it returns fixed catalog contents with prices and session evidence. It stops short of describing ordering or response shape, but for a read-only, zero-parameter listing that is a minor gap.

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?

A single front-loaded sentence with the resource, the exact scope, the returned data, and the free-access constraint. No filler and nothing buried.

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?

There is no output schema, yet the description conveys what comes back (albums, tracks, prices, per-track session evidence), which is what an agent needs to decide whether a follow-up call is necessary. Ordering and exact response format are left unspecified, but that is a small omission for a simple enumeration tool.

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 schema has zero properties, so there are no parameters to mis-document and the baseline applies. The description correctly implies no filtering arguments are needed because the entire catalog is returned.

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?

States a specific verb ('List') and resource ('wellness music catalog') and quantifies the scope: 9 albums, 27 tracks, with prices and per-track session evidence. It is clearly a browse/enumerate tool rather than a single-item fetch like get_track_evidence, though it never names the siblings it differs from.

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?

'No payment required' implies this is the free browse step before purchase_track/purchase_album, which is useful context. However, there is no explicit when-to-use or when-not-to-use statement and no sibling is named, so the agent must infer that this listing should precede the purchase 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.