Skip to main content
Glama

Get compute pricing history and research

get_compute_pricing
Read-onlyIdempotent

Read stored OpenRouter baseline list prices, transparent median membership, GPU-hour rental prices per GPU family and tier (GetDeploying CC BY dataset, Azure, Oracle OCI list prices where enabled, and a cross-source composite; min/median/max and offer counts in metadata), licensed Pricify GPU price/stock history (vga.live + rtx.live), reserved GPU-hour prices by term (gpu_terms, kind gpu_term: gputerm:getdeploying:h100:12mo and 1, 3, 6, 24 and 36 months, listed prices, often few providers), Pricify memory, SSD, hard drive and CPU prices (components, kind component; search such as 64GB DDR5), daily Pricify retail indices (retail_indexes, kind retail_index; such as pricify-index:ddr5, usable with view=correlation), the Pricify forecast record (retail_forecasts: daily model low plus 7/30/90-day p10/p50/p90; while metadata.method is naive, p50 is today's price, a no-change baseline and not a prediction), Gambit-hosted retail (source gambit_retail, kind retail: daily Radeon AI PRO R9700 listed price at one retailer, which may be out of stock — search R9700), semiconductor fundamentals with history (fundamentals, kind fundamental; search such as nanya or micron): TWSE monthly revenue for ~27 Taiwan chain companies (semis:twse::revenue, NT$ thousand, monthly from when collection started, basis reported or reported_prior) and SEC quarterly revenue, gross profit, operating income, capex and inventory for ~27 US filers from 2022 (semis:sec::, filer currency, basis reported or derived from year-to-date filings; a loss has value null and metadata.signed_value), and Taiwan MOEA monthly export orders by product since 1984 (semis:moea:export_orders:<electronics|optical|electrical|machinery|basic_metals|chemicals|plastics_rubber>, USD million; electronics orders lead chip shipments by one to three months), per-provider model serving speed and price from OpenRouter's endpoints (serving, kind serving; search a model such as glm-5.2: openrouter_serving:model:: every 3 hours with endpoints, output_min and output_median USD/Mtok, throughput_p50_median and throughput_p50_best tokens/s, ttft_p50_median ms and usd_per_stream_hour_median, the derived USD one stream at typical speed bills per hour; openrouter_serving:endpoint:::<output|throughput_p50|ttft_p50> daily; OpenRouter's last-30-minute measurements of its own traffic, not a benchmark), local-AI adoption from Hugging Face GGUF downloads (usage, kind usage: hf_gguf:base:<org/model>:downloads_30d and :share_pct of the top-100 GGUF text repos, hf_gguf:repo::downloads_30d, hf_gguf:index:top100:downloads_30d; daily, each a trailing-30-day count, not daily downloads), developer adoption from package downloads (also kind usage, sources pypi_downloads and npm_downloads: pypi::downloads_day and npm::downloads_day, one UTC day each, for inference engines such as vllm and sglang, local runtimes such as llama-cpp-python and mlx-lm, AI SDKs such as openai and @anthropic-ai/sdk, routers, MCP SDKs and agent CLIs such as @anthropic-ai/claude-code and @openai/codex; PyPI excludes mirrors, both include CI installs),, the settlement networks AI agents use from DefiLlama (rails, kind rail, source defillama_rails: rail_defi_tvl_usd: and rail_stablecoin_supply_usd: per day, rail_stablecoin_supply_usd:: for the largest issuers, rail_spot_dex_volume_usd: and rail_gas_fees_usd: per complete month with _daily ids per day, and hl_exchange_fees_usd / hl_exchange_revenue_usd:<perps|spot> for Hyperliquid's exchange; rails include ethereum, solana, base, arbitrum, hyperliquid, plasma, robinhood_chain, tempo, stable, arc and elysium; DefiLlama revises recent history and the first stored value is kept) and rights-enabled ORNN history (api:read). For monthly or quarterly series pass start up to 366 days before end. view=catalog discovers series_id: by default (detail=summary) it returns series counts per kind and source plus at most 100 series without metadata, so narrow with kind and search; detail=full returns up to 2000 series with metadata, about 1.2 MB unfiltered. view=history returns capped genuine observations for one series, default window 90 days: history.available says what is stored and history.note says when the window left some out; detail=full adds list metadata such as index membership. view=correlation returns one series' returns against stored Databento equity closes over the same span at the series' cadence (a weekly compute return pairs with the equity return over those days), with calendar-day lag, at least 10 pairs for a Pearson, status insufficient_data with a reason otherwise, and an availability-aware hypothetical backtest. history and correlation leave the catalog lists empty. view=forecast_record reads Gambit's sealed, log-only forecast ledger: the methods, the chain's head digest, a scoreboard per method, group and horizon (each compared with no-change, and claim_ready false until 26 independent starts), and with series_id that target's latest forecasts. Not a recommendation and no claim of skill. Returns are fractions. No forward filling, trading or collection on read. Missing history/rights is explicit; a refused query says why.

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

Input Schema

NameRequiredDescriptionDefault
endNoISO date (read as 00:00 UTC) or timestamp with an offset, not in the future. Default: now.
kindNoCatalog only: one kind of series.
viewNocatalog
startNoISO date (read as 00:00 UTC) or timestamp with an offset. Default: 90 days before end. At most 366 days before end.
detailNosummary (default) drops catalog metadata and list-valued point metadata; full keeps them.summary
searchNoCatalog only: case-insensitive text in series_id or label, such as h100.
symbolNoUnprefixed equity ticker. Required for correlation.
intervalNoHistory only; correlation always reads daily buckets.
lag_daysNoPositive means compute leads equity.
series_idNoRequired for history and correlation. With forecast_record, a target such as pricify-index:ddr5.
max_pointsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / detail / description
      Previous value: -"summary drops catalog metadata and list-valued point metadata; full keeps them. The REST default is full."New value: +"summary (default) drops catalog metadata and list-valued point metadata; full keeps them."
  2. Changed1 schema field changed
    • changedInput schema / properties / kind / enum
      Previous value: -[
      -  "model",
      -  "index",
      -  "gpu_hour",
      -  "lab_token",
      -  "retail",
      -  "retail_forecast",
      -  "component",
      -  "retail_index",
      -  "gpu_term",
      -  "fundamental",
      -  "serving",
      -  "usage"
      -]New value: +[
      +  "model",
      +  "index",
      +  "gpu_hour",
      +  "lab_token",
      +  "retail",
      +  "retail_forecast",
      +  "component",
      +  "retail_index",
      +  "gpu_term",
      +  "fundamental",
      +  "serving",
      +  "usage",
      +  "rail"
      +]
  3. Changed1 schema field changed
    • changedInput schema / properties / kind / enum
      Previous value: -[
      -  "model",
      -  "index",
      -  "gpu_hour",
      -  "lab_token",
      -  "retail",
      -  "retail_forecast",
      -  "component",
      -  "retail_index",
      -  "gpu_term",
      -  "fundamental"
      -]New value: +[
      +  "model",
      +  "index",
      +  "gpu_hour",
      +  "lab_token",
      +  "retail",
      +  "retail_forecast",
      +  "component",
      +  "retail_index",
      +  "gpu_term",
      +  "fundamental",
      +  "serving",
      +  "usage"
      +]
  4. Changed1 schema field changed
    • changedInput schema / properties / kind / enum
      Previous value: -[
      -  "model",
      -  "index",
      -  "gpu_hour",
      -  "lab_token",
      -  "retail",
      -  "retail_forecast",
      -  "component",
      -  "retail_index",
      -  "gpu_term"
      -]New value: +[
      +  "model",
      +  "index",
      +  "gpu_hour",
      +  "lab_token",
      +  "retail",
      +  "retail_forecast",
      +  "component",
      +  "retail_index",
      +  "gpu_term",
      +  "fundamental"
      +]
  5. Changed1 schema field changed
    • changedInput schema / properties / kind / enum
      Previous value: -[
      -  "model",
      -  "index",
      -  "gpu_hour",
      -  "lab_token",
      -  "retail",
      -  "retail_forecast",
      -  "component",
      -  "retail_index"
      -]New value: +[
      +  "model",
      +  "index",
      +  "gpu_hour",
      +  "lab_token",
      +  "retail",
      +  "retail_forecast",
      +  "component",
      +  "retail_index",
      +  "gpu_term"
      +]
  6. Changed3 schema fields changed
    • changedInput schema / properties / kind / enum
      Previous value: -[
      -  "model",
      -  "index",
      -  "gpu_hour",
      -  "lab_token",
      -  "retail",
      -  "retail_forecast"
      -]New value: +[
      +  "model",
      +  "index",
      +  "gpu_hour",
      +  "lab_token",
      +  "retail",
      +  "retail_forecast",
      +  "component",
      +  "retail_index"
      +]
    • changedInput schema / properties / series_id / description
      Previous value: -"Required for history and correlation."New value: +"Required for history and correlation. With forecast_record, a target such as pricify-index:ddr5."
    • changedInput schema / properties / view / enum
      Previous value: -[
      -  "catalog",
      -  "history",
      -  "correlation"
      -]New value: +[
      +  "catalog",
      +  "history",
      +  "correlation",
      +  "forecast_record"
      +]
  7. Changed9 schema fields changed
    • addedInput schema / properties / detail
      Added value: +{
      +  "default": "summary",
      +  "description": "summary drops catalog metadata and list-valued point metadata; full keeps them. The REST default is full.",
      +  "enum": [
      +    "summary",
      +    "full"
      +  ],
      +  "type": "string"
      +}
    • addedInput schema / properties / end / description
      Added value: +"ISO date (read as 00:00 UTC) or timestamp with an offset, not in the future. Default: now."
    • addedInput schema / properties / interval / description
      Added value: +"History only; correlation always reads daily buckets."
    • addedInput schema / properties / kind
      Added value: +{
      +  "description": "Catalog only: one kind of series.",
      +  "enum": [
      +    "model",
      +    "index",
      +    "gpu_hour",
      +    "lab_token",
      +    "retail",
      +    "retail_forecast"
      +  ],
      +  "type": "string"
      +}
    • addedInput schema / properties / lag_days / description
      Added value: +"Positive means compute leads equity."
    • addedInput schema / properties / search
      Added value: +{
      +  "description": "Catalog only: case-insensitive text in series_id or label, such as h100.",
      +  "maxLength": 64,
      +  "type": "string"
      +}
    • addedInput schema / properties / series_id / description
      Added value: +"Required for history and correlation."
    • addedInput schema / properties / start / description
      Added value: +"ISO date (read as 00:00 UTC) or timestamp with an offset. Default: 90 days before end. At most 366 days before end."
    • addedInput schema / properties / symbol / description
      Added value: +"Unprefixed equity ticker. Required for correlation."
  8. Added

TDQS

A4.1/5.0
Behavior5/5

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

The description adds substantial behavior beyond the read-only/idempotent annotations: no forward filling or trading on read, explicit missing history/rights, refusal reasons, catalog size limits, history capping and availability notes, correlation's minimum-pair requirement, forecast ledger claim_ready semantics, and DefiLlama revision behavior. These details materially help an agent understand what the tool will and will not return.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single massive, semicolon-heavy block that enumerates dozens of series identifiers and data sources before the view semantics are explained. Much of that catalog is discoverable through view=catalog, so the length is not fully justified, and the structure makes it difficult to parse. It is front-loaded with the core read action, but overall it is overstuffed rather than concise.

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?

For an 11-parameter, multi-view tool with no output schema, the description covers the important operational details: mode selection, catalog limits, history window behavior, correlation requirements and failure status, forecast ledger semantics, and read-time side-effect exclusions. An agent has enough context to choose a view and interpret likely outcomes without needing an output schema.

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 high (82%), so the baseline is 3, but the description adds meaningful semantics for series_id patterns, the purpose of each view, detail=summary versus full, start-window limits, interval applicability, and lag_days sign interpretation. It does not document max_points in prose and the series_id catalog is sprawling rather than systematically mapped to parameters, but the added meaning is substantial.

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 verb and resource: 'Read stored OpenRouter baseline list prices... GPU-hour rental prices... licensed Pricify GPU price/stock history...' It clearly identifies the tool as a read-only pricing/research data retrieval tool across enumerated sources. The purpose is unambiguous, though the dense enumeration makes the core scope harder to extract than a crisp one-line statement.

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 mode-based guidance: view=catalog discovers series_id, view=history returns observations, view=correlation pairs returns with equity closes, and view=forecast_record reads the forecast ledger. It also advises narrowing catalog results with kind and search, and notes that monthly/quarterly series require start up to 366 days before end. It does not explicitly name sibling alternatives or state when not to use this tool, but the internal usage context is strong.

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.

Resources