Skip to main content
Glama

Compare credit pack prices

compare_credits
Read-onlyIdempotent

Compare credit pack prices (extra usage credits sold on top of a subscription, such as ChatGPT credits) across regions, normalised to the price per 100 credits in one currency. Answers questions like "where are ChatGPT credits cheapest?".

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

Input Schema

NameRequiredDescriptionDefault
packNoall (default), unit for single-credit prices, or a pack quantity such as 1000.all
pageNo
sortNoprice_asc: cheapest per 100 credits first (default); price_desc; region: alphabetical.price_asc
limitNo
localeNoLanguage for region and plan names: en (default) or zh.en
regionNoOptional filter by region code or name.
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.chatgpt
currencyNoISO 4217 currency for converted reference prices, e.g. USD, CNY, EUR. Defaults to USD for en and CNY for zh.

Output Schema

NameRequiredDescriptionDefault
urlYes
packYes
pageYes
rowsYes
channelYes
productYes
currencyYes
totalPagesYes
fxUpdatedAtYes
dataUpdatedAtYes
availablePacksYes
matchingOffersYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field 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."
  2. Changed4 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"
  3. 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, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely non-obvious behavior: prices are normalised to a per-100-credits figure in a single currency, which explains how results are computed. It does not mention pagination or result ordering, but those are covered by the schema and output schema.

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 tight sentences: the first front-loads what is compared and how values are normalised, the second supplies a concrete motivating question. No filler or duplicated field documentation.

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 9-parameter tool with rich schema descriptions, annotations, and an output schema, the description covers purpose, unit normalisation, and the core question it answers. The main missing element is explicit disambiguation from compare_prices and get_reference_prices, which would help an agent choose correctly.

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 description coverage is 78%, near the high-coverage baseline where the schema carries the burden; detailed parameter docs (pack, sort, channel, currency, locale defaults) live in the schema. The description adds only loose hints ('across regions', 'in one currency') and never explains pack selection or the web vs app_store channel choice.

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 (compare) and a well-defined resource (credit pack prices), and clarifies the resource as 'extra usage credits sold on top of a subscription, such as ChatGPT credits', which implicitly distinguishes it from plan-price siblings like compare_prices. It stops short of explicitly contrasting with those siblings.

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?

The example question "where are ChatGPT credits cheapest?" gives a concrete usage context that makes the intended scenario obvious. There are no explicit exclusions or named alternatives, so this is clear context without routing guidance.

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.