Skip to main content
Glama

Price history

get_price_history
Read-onlyIdempotent

Weekly history. With index_code: the index series (benchmark level, May 2026 = 100 or October 19, 2026 = 100 for regional EUR and CNY versions, and the spot price with its 25th and 75th percentiles) for up to 260 weeks; free. With model_name: every vendor's price for that model week by week, showing when each SKU was repriced; Attic Standard MCP PRO.

Token prices are per 1,000 tokens; other modalities use their own unit (per image, per second, per minute, per 1,000 characters).

Examples:

  • "How has the neocloud index moved since May?" -> index_code="NCL"

  • "Has anyone cut the price of DeepSeek V3 this quarter?" -> model_name="DeepSeek V3", weeks=13

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_price_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
weeksNoHow many weeks back (default 26)
vendorNoWith model_name: limit to one vendor. PRO.
directionNoPricing direction
index_codeNoIndex history, e.g. 'TXT', 'DEV', 'OSS', 'AIPI TXT GLB' or a regional version such as 'TXT CNY'. Free.
model_nameNoModel price history across every vendor that sells it, e.g. 'GPT-4o'. PRO.
_atom_api_keyNoYour Attic Standard MCP PRO key for vendor- and SKU-level data. Omit for the free tier.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / index_code / description
      Previous value: -"Index history, e.g. 'TXT', 'DEV', 'OSS' or 'AIPI TXT GLB'. Free."New value: +"Index history, e.g. 'TXT', 'DEV', 'OSS', 'AIPI TXT GLB' or a regional version such as 'TXT CNY'. Free."
  2. 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 readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds useful context about free versus PRO access, the 260-week maximum, and what the returned series contains, but it does not discuss rate limits or other operational constraints.

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 description is front-loaded with the core behavior and then supplies units and examples. It is generally efficient, though the parenthetical benchmark-level details are dense and could be tightened.

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 no output schema, the description does a good job explaining what each mode returns: index levels, spot price percentiles, and week-by-week vendor pricing. It is nearly complete for invocation, though it could say more about how direction affects results.

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

Parameters4/5

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

Schema description coverage is 100%, so the baseline is 3. The description adds value by giving examples for index_code and model_name, clarifying that weeks controls lookback, and noting that vendor and model_name are PRO-scoped, though direction and _atom_api_key are left to the schema.

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 clearly states that this tool returns weekly price history and distinguishes the two main modes: index_code for index series and model_name for vendor-by-vendor model pricing. It is specific about the resource and scope, but it does not explicitly differentiate itself from siblings such as get_index_benchmarks or compare_prices.

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 gives clear usage conditions for the two primary modes and includes concrete examples that map natural-language questions to parameters. It does not explicitly state when not to use this tool or name alternative sibling tools, so it falls short of full alternative 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.