Skip to main content
Glama

Price indices

price_index
Read-onlyIdempotent

The trial indices: token price indices for flagship, mid and small models (100 on the base date) with their recent moves and announced changes, and the GPU-hour reference price per GPU model. Use it for "are model prices going up or down" rather than one model's price.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior3/5

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

The annotations already declare a safe, idempotent, closed-world read, so the description only needs to add context. It does add the index base (100 on the base date) and the scope of what is included (recent moves, announced changes, GPU-hour reference price), but says nothing about update cadence, how 'recent' is bounded, or response shape.

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 resource and followed immediately by the routing hint, with no filler. The opening 'The trial indices:' is a slightly puzzling label that costs a moment of clarity.

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 parameters and no output schema, the description carries the burden of explaining returns, which it largely does by naming the index families and the GPU-hour reference price. Gaps are minor: coverage of which model families, index update frequency, and units/format for the GPU-hour price.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate and the baseline applies. The description compensates usefully by explaining what the index values mean (base date = 100).

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a concrete resource (token price indices for flagship/mid/small models plus a GPU-hour reference price) and pins down the semantics with '(100 on the base date)'. It also distinguishes itself from single-price tools by framing itself as the trend view rather than one model's price.

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?

Explicitly says to use it for 'are model prices going up or down' rather than for one model's price, which rules out the check_price/get_price style siblings by category. It does not address when to prefer price_changes, gpu_prices or share_price, so the routing is clear but not exhaustive.

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.