Skip to main content
Glama

Recent and announced price changes

price_changes
Read-onlyIdempotent

Observed changes between successive records of the same model and channel, plus vendor-announced changes with their effective dates. List prices as published by each channel at observed_at, USD per 1M tokens unless stated; China-site price lists are in CNY, listed separately and never converted. Standard (on-demand) plan unless service_plan says otherwise. The channel's own page is authoritative. Aggregator prices are the marketplace's own and never the reference. A missing price is unknown, not free. Not purchasing advice.

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

Input Schema

NameRequiredDescriptionDefault
daysNoLook-back window, default 30

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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 readOnly/idempotent/non-destructive, and the description adds substantial context beyond them: currency rules (China-site CNY lists kept separate and never converted), source authority (channel page over aggregator marketplace), plan default (standard on-demand unless service_plan says otherwise), and the 'missing price is unknown, not free' rule. It stops short of stating refresh cadence or coverage limits.

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?

The purpose is front-loaded in the first sentence and the remaining sentences are short, discrete semantic rules rather than padding. The closing 'Not purchasing advice' is a disclaimer that earns little space, but overall there is minimal waste.

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 single-parameter read tool with no output schema, the description covers what is returned conceptually (observed deltas plus announced changes with effective dates) and the price semantics needed to interpret values. It is slightly thin on the shape of returned records, which matters given there is no output schema.

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?

With a single parameter and 100% schema description coverage, the schema already documents 'days' as a 1-365 look-back window defaulting to 30. The description never mentions the parameter, so it adds no meaning here and the baseline of 3 applies.

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 opens with a specific definition of the resource: 'Observed changes between successive records of the same model and channel, plus vendor-announced changes with their effective dates.' That distinguishes change-history from a point price, but it never names or contrasts the closest siblings (get_price, check_price, price_index), so an agent must infer the split.

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 is only implied: the presence of a look-back window and the emphasis on 'changes between successive records' signals this is for history/deltas rather than current pricing, but there is no explicit when-to-use or when-not-to-use statement and no alternative tool is named.

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.