Skip to main content
Glama

Attic Standard index benchmarks

get_index_benchmarks
Read-onlyIdempotent

The Attic Standard price indexes for AI inference: every published index at the week the site shows.

Six families: Modality (text, multimodal, image, video, audio, voice, embeddings), Channel (model developers, cloud marketplaces, inference platforms, neoclouds), Tier (flagship, core, compact), License (open weights, restricted weights, proprietary), Origin (United States, China) and Use case (reasoning, coding).

For each index and direction (input, cached input, output) it returns the benchmark level (May 2026 = 100; regional EUR and CNY versions October 19, 2026 = 100) with week, month and vs-base changes, the spot price (median, p25, p75, in dollars, or in euros or yuan for regional versions) with its own week, month and vs-base changes, and coverage counts with the May 2026 basket size, flagged where the basket has changed materially since the base.

Free: fully public, the same figures atticstandard.com publishes. Token prices are per 1,000 tokens; other modalities use their own unit (per image, per second, per minute, per 1,000 characters).

Examples:

  • "Where is text inference priced this week?" -> index_code="TXT"

  • "Compare the four channels" -> index_category="Channel"

  • "Open-weight versus proprietary" -> index_category="License"

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

Input Schema

NameRequiredDescriptionDefault
index_codeNoOne index, e.g. 'TXT', 'NCL', 'FLG', the full code 'AIPI TXT GLB', or a regional version such as 'TXT CNY' or 'AIPI MML EUR'. Omit for all published indexes.
_atom_api_keyNoYour Attic Standard MCP PRO key for vendor- and SKU-level data. Omit for the free tier.
index_categoryNoIndex family: 'Modality', 'Channel', 'Tier', 'License', 'Origin', 'Use case'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / index_code / description
      Previous value: -"One index, e.g. 'TXT', 'NCL', 'FLG' or the full code 'AIPI TXT GLB'. Omit for all published indexes."New value: +"One index, e.g. 'TXT', 'NCL', 'FLG', the full code 'AIPI TXT GLB', or a regional version such as 'TXT CNY' or 'AIPI MML EUR'. Omit for all published indexes."
  2. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), and the description adds genuinely non-obvious behavior: free vs PRO key gating, per-1,000-token versus per-image/second/minute/character units, the May 2026 and October 19, 2026 base conventions, and material-basket-change flagging. Rate limits and pagination are unaddressed, so not a 5.

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?

It is front-loaded with the one-line purpose, then the family taxonomy, then the return shape, then usage examples — a sensible ordering. It is long, and the family enumeration in paragraph two is dense, but nearly every clause carries information an agent needs to construct a call.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/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 carries the full burden of explaining returns and does so precisely: benchmark level with week/month/vs-base deltas, spot price medians and p25/p75 with their own deltas, and coverage counts with basket size. For a complex, multi-family index tool with three optional parameters, nothing essential is missing.

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 coverage is 100%, so a 3 is the floor, but the description earns more: it enumerates the actual members of each family (Modality: text, multimodal, image, video, audio, voice, embeddings; Channel: model developers, cloud marketplaces, inference platforms, neoclouds) which the schema only names as categories. That materially helps an agent pick a valid `index_category` value.

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 first sentence names a specific resource (the Attic Standard price indexes for AI inference) and scope (every published index at the current week's cut). It is clear what is returned, but it never explicitly distinguishes itself from `compare_prices` or `get_price_history`, so an agent choosing between them gets no routing signal from the text.

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 three worked examples ('Where is text inference priced this week?' -> index_code="TXT", 'Compare the four channels' -> index_category="Channel") give concrete when-to-use context, and the free-tier statement tells the agent no key is required. There are no explicit exclusions or named alternatives, which keeps it short of a 5.

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.