Skip to main content
Glama

Recent price changes

get_recent_price_changes
Read-onlyIdempotent

List monthly subscription price changes AISub recorded across all regions in the last N days, newest first. Use it for questions like "which countries changed ChatGPT prices this month?".

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

Input Schema

NameRequiredDescriptionDefault
daysNoLook-back window in days, 1–90.
limitNo
localeNoLanguage for region and plan names: en (default) or zh.en
productNoOnly changes for this product.

Output Schema

NameRequiredDescriptionDefault
urlYes
daysYes
totalYes
changesYes
trackedSinceYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedOutput schema / properties / changes / items / properties / percent
      Added value: +{
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
    • addedOutput schema / properties / changes / items / properties / periodConfidence
      Added value: +{
      +  "enum": [
      +    "explicit",
      +    "inferred",
      +    "unknown"
      +  ],
      +  "type": "string"
      +}
    • addedOutput schema / properties / changes / items / properties / previousPeriodConfidence
      Added value: +{
      +  "enum": [
      +    "explicit",
      +    "inferred",
      +    "unknown"
      +  ],
      +  "type": "string"
      +}
    • addedOutput schema / properties / changes / items / properties / reviewMethod
      Added value: +{
      +  "enum": [
      +    "automatic",
      +    "manual",
      +    "unreviewed"
      +  ],
      +  "type": "string"
      +}
  2. Changed3 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"
      +  }
      +]
    • removedInput schema / properties / product / enum
      Removed value: -[
      -  "chatgpt",
      -  "claude",
      -  "gemini",
      -  "perplexity",
      -  "grok"
      -]
    • removedInput schema / properties / product / type
      Removed value: -"string"
  3. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds two genuinely behavioral facts beyond that: results are drawn from AISub's own records and are returned newest-first. It says nothing about truncation at limit (default 20, max 50) or whether results are capped before the full window is covered.

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 with no filler: the scope and ordering constraint is front-loaded and the example question follows as illustration. Nothing is repeated from the schema or annotations.

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 read-only list tool with an output schema, full annotations, and mostly documented parameters, the description covers what the agent needs to select and call it. The remaining gap is disambiguation from get_price_history and compare_prices, which is left to inference.

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 75%, with days, locale, and product documented inline, so the schema carries most of the load. The description only reinforces the days window ('last N days') and gives no extra meaning for limit, locale, or the app_-prefixed product ID form. Baseline 3 is appropriate.

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 gives a specific verb and resource ('List monthly subscription price changes'), plus scope ('across all regions in the last N days') and ordering ('newest first'). The 'across all regions' phrasing implicitly separates it from get_region_prices and compare_prices, but no sibling is named explicitly.

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?

It supplies a concrete usage example ('which countries changed ChatGPT prices this month?') that clearly signals the intended question shape. It offers no when-not-use guidance or routing to get_price_history / compare_prices for per-product or cross-product comparisons, so the agent must infer the boundary.

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.