Skip to main content
Glama

All plan prices in one region

get_region_prices
Read-onlyIdempotent

Show every plan price of one product in one country or region, for each sales channel and billing interval, with its rank among all regions and its difference from the United States. Answers questions like "how much does ChatGPT cost in Japan?" or "is Claude cheaper in India than in the US?".

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "region": "<region>"
    },
    "name": "get_region_prices"
  }
}

Input Schema

NameRequiredDescriptionDefault
localeNoLanguage for region and plan names: en (default) or zh.en
regionYesCountry or region as an ISO 3166 code (JP), English name (Japan) or Chinese name (日本).
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
notesYes
pricesYes
regionYes
missingYes
productYes
currencyYes
fxUpdatedAtYes
observationsYes
dataUpdatedAtYes
historicalObservationsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedOutput schema / properties / historicalObservations
      Added value: +{
      +  "items": {
      +    "additionalProperties": false,
      +    "properties": {
      +      "amount": {
      +        "type": "string"
      +      },
      +      "currency": {
      +        "type": "string"
      +      },
      +      "fetchedAt": {
      +        "type": "string"
      +      },
      +      "interval": {
      +        "enum": [
      +          "month",
      +          "year"
      +        ],
      +        "type": "string"
      +      },
      +      "intervalSource": {
      +        "type": "string"
      +      },
      +      "name": {
      +        "type": "string"
      +      },
      +      "planKey": {
      +        "type": "string"
      +      },
      +      "state": {
      +        "const": "not_observed",
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "planKey",
      +      "name",
      +      "amount",
      +      "currency",
      +      "fetchedAt",
      +      "state"
      +    ],
      +    "type": "object"
      +  },
      +  "type": "array"
      +}
    • changedOutput schema / required
      Previous value: -[
      -  "product",
      -  "region",
      -  "currency",
      -  "prices",
      -  "observations",
      -  "missing",
      -  "dataUpdatedAt",
      -  "fxUpdatedAt",
      -  "notes",
      -  "url"
      -]New value: +[
      +  "product",
      +  "region",
      +  "currency",
      +  "prices",
      +  "observations",
      +  "historicalObservations",
      +  "missing",
      +  "dataUpdatedAt",
      +  "fxUpdatedAt",
      +  "notes",
      +  "url"
      +]
  2. Changed4 schema fields changed
    • addedOutput schema / properties / observations
      Added value: +{
      +  "items": {
      +    "additionalProperties": false,
      +    "properties": {
      +      "amount": {
      +        "type": "string"
      +      },
      +      "currency": {
      +        "type": "string"
      +      },
      +      "fetchedAt": {
      +        "type": "string"
      +      },
      +      "name": {
      +        "type": "string"
      +      },
      +      "period": {
      +        "const": "unknown",
      +        "type": "string"
      +      },
      +      "planKey": {
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "name",
      +      "amount",
      +      "currency",
      +      "fetchedAt",
      +      "planKey",
      +      "period"
      +    ],
      +    "type": "object"
      +  },
      +  "type": "array"
      +}
    • addedOutput schema / properties / prices / items / properties / periodBasis
      Added value: +{
      +  "enum": [
      +    "source",
      +    "pair",
      +    "default",
      +    "manual",
      +    "unknown"
      +  ],
      +  "type": "string"
      +}
    • changedOutput schema / properties / prices / items / required
      Previous value: -[
      -  "status",
      -  "localAmount",
      -  "localCurrency",
      -  "amountBasis",
      -  "tax",
      -  "referencePrice",
      -  "yearlyTotal",
      -  "vsUs",
      -  "quoteUpdatedAt",
      -  "stale",
      -  "channel",
      -  "plan",
      -  "planName",
      -  "unit",
      -  "interval",
      -  "rank",
      -  "pricedRegions"
      -]New value: +[
      +  "periodBasis",
      +  "status",
      +  "localAmount",
      +  "localCurrency",
      +  "amountBasis",
      +  "tax",
      +  "referencePrice",
      +  "yearlyTotal",
      +  "vsUs",
      +  "quoteUpdatedAt",
      +  "stale",
      +  "channel",
      +  "plan",
      +  "planName",
      +  "unit",
      +  "interval",
      +  "rank",
      +  "pricedRegions"
      +]
    • changedOutput schema / required
      Previous value: -[
      -  "product",
      -  "region",
      -  "currency",
      -  "prices",
      -  "missing",
      -  "dataUpdatedAt",
      -  "fxUpdatedAt",
      -  "notes",
      -  "url"
      -]New value: +[
      +  "product",
      +  "region",
      +  "currency",
      +  "prices",
      +  "observations",
      +  "missing",
      +  "dataUpdatedAt",
      +  "fxUpdatedAt",
      +  "notes",
      +  "url"
      +]
  3. 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"
  4. First observed

TDQS

A3.7/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 substantive behavioral context beyond them: results include per-channel and per-interval breakdowns, a rank among all regions, and a delta against the United States. It stops short of describing pagination or result size limits, which would be the remaining gap.

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 sentences, front-loaded with the core capability before the illustrative examples. The example questions earn their place by aiding routing, though they are essentially restatements of the same capability and could be trimmed. No filler or hedging.

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?

With an output schema present, the description does not need to explain return values and correctly focuses on scope and the semantic nature of the results. All four parameters are schema-documented, so nothing critical is missing. The only shortfall is the absence of any routing hint versus the comparison and reference-price siblings.

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%, so region, product, locale, and currency are all documented in the schema itself, which sets the baseline at 3. The description reinforces the product/region scoping and mentions the sales-channel and billing-interval breakdown, but says nothing about locale or currency behavior (including the en/CNY vs USD default). Little meaning is added beyond 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?

States a specific verb and resource with clear scope: every plan price for one product in one region, broken out by sales channel and billing interval. It also names the derived values returned (regional rank, difference from the US). It never mentions the sibling tools it might be confused with, such as compare_prices or get_reference_prices, so an agent must infer the boundary itself.

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?

Usage context is conveyed only through example questions ('how much does ChatGPT cost in Japan?'), which implies the scenario but does not state when to prefer this tool over compare_prices or get_reference_prices. The second example ('is Claude cheaper in India than in the US?') plausibly overlaps with a comparison sibling, and the description does not resolve that ambiguity. Guidance exists but is inferred rather than explicit.

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.