Skip to main content
Glama

List products, plans and regions

list_catalog
Read-onlyIdempotent

List the AI subscription products, sales channels, plan keys, billing intervals and regions that AISub tracks. Call without arguments for an overview; pass a product (and optionally a channel) to also get its region codes and the currencies available for conversion. Use the returned plan keys and region codes with the other tools.

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
localeNoLanguage for region and plan names: en (default) or zh.en
channelNoSales channel: web (regional website prices) or app_store (iOS). Defaults to web for ChatGPT and app_store for other products. Claude website reference prices use get_reference_prices.
productNoProduct key returned by list_catalog, including dynamically registered app_<apple-id> products.

Output Schema

NameRequiredDescriptionDefault
productsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedOutput schema / properties / products / items / properties / channels / items / properties / plans / items / properties / hasUnknownPeriod
      Added value: +{
      +  "type": "boolean"
      +}
    • changedOutput schema / properties / products / items / properties / channels / items / properties / plans / items / required
      Previous value: -[
      -  "key",
      -  "name",
      -  "unit",
      -  "intervals"
      -]New value: +[
      +  "key",
      +  "name",
      +  "unit",
      +  "intervals",
      +  "hasUnknownPeriod"
      +]
  2. Changed3 schema fields changed
    • changedInput schema / properties / channel / description
      Previous value: -"Sales channel: web (ChatGPT website checkout, ChatGPT only) or app_store (iOS in-app purchase). Defaults to web for ChatGPT and app_store for other products."New value: +"Sales channel: web (regional website prices) or app_store (iOS). Defaults to web for ChatGPT and app_store for other products. Claude website reference prices use get_reference_prices."
    • addedOutput schema / properties / products / items / properties / channels / items / properties / quoteScope
      Added value: +{
      +  "const": "regional",
      +  "type": "string"
      +}
    • changedOutput schema / properties / products / items / properties / channels / items / required
      Previous value: -[
      -  "channel",
      -  "plans",
      -  "regionCount",
      -  "pricedRegionCount"
      -]New value: +[
      +  "channel",
      +  "quoteScope",
      +  "plans",
      +  "regionCount",
      +  "pricedRegionCount"
      +]
  3. Changed5 schema fields changed
    • addedInput schema / properties / product / anyOf
      Added value: +[
      +  {
      +    "enum": [
      +      "chatgpt",
      +      "claude",
      +      "gemini",
      +      "perplexity",
      +      "grok"
      +    ],
      +    "type": "string"
      +  },
      +  {
      +    "pattern": "^app_[1-9]\\d{5,14}$",
      +    "type": "string"
      +  }
      +]
    • changedInput schema / properties / product / description
      Previous value: -"Product: chatgpt, claude, gemini, perplexity or grok."New value: +"Product key returned by list_catalog, including dynamically registered app_<apple-id> products."
    • removedInput schema / properties / product / enum
      Removed value: -[
      -  "chatgpt",
      -  "claude",
      -  "gemini",
      -  "perplexity",
      -  "grok"
      -]
    • removedInput schema / properties / product / type
      Removed value: -"string"
    • removedOutput schema / properties / products / items / properties / product / enum
      Removed value: -[
      -  "chatgpt",
      -  "claude",
      -  "gemini",
      -  "perplexity",
      -  "grok"
      -]
  4. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds behavior beyond them by disclosing that output content varies with arguments (overview alone vs. region codes and currencies when a product is passed). It does not discuss pagination or output volume, but the output schema exists to cover return shape.

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?

Two sentences, zero filler, with the no-argument default front-loaded before the parameterized variant. Each clause carries actionable information.

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 zero-required-parameter, read-only discovery tool with a full output schema and complete annotation coverage, nothing an agent needs to call it correctly is missing. The description supplies the downstream purpose of the returned keys, which the structured fields cannot convey.

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

Parameters3/5

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

Schema coverage is 100% and already documents locale, channel defaults (web vs. app_store per product) and the app_<apple-id> product pattern. The description only adds the relational nuance that channel is optional alongside product; with the schema doing the heavy lifting, this is baseline 3.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Names a specific verb and resource ('List the AI subscription products, sales channels, plan keys, billing intervals and regions') and enumerates exactly what is returned. The closing sentence positions it as the discovery entry point relative to siblings like get_region_prices and compare_prices, so an agent can distinguish it without opening another schema.

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?

Gives concrete usage variants: 'Call without arguments for an overview; pass a product (and optionally a channel) to also get its region codes and the currencies available for conversion.' It also states downstream usage ('Use the returned plan keys and region codes with the other tools'). It lacks an explicit when-not-to-use clause or named alternative, so it stops short of a 5.

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.