Skip to main content
Glama

Developer Utilities & Validators (Tanod)

get_gpu_price_index

Read-onlyIdempotent

utilpeek: GPU price index: daily H100, H200, A100 rental price per GPU-hour over time. Returns a GPU chip's daily rental price history: lowest and median on-demand list price, lowest spot, Akash median bid and free GPUs. List prices and marketplace bids, not executed trades. Days without a snapshot are missing, not interpolated. Typically under 0.1 s. Price: USD 0.002. Free: 10 utilpeek calls per IP per UTC day. Docs: https://tanod.dev/learn/cloud-gpu-price-api.html

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "chip": "<chip>"
    },
    "name": "get_gpu_price_index"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoLast UTC day, YYYY-MM-DD (default: the newest day recorded).
chipYesGPU chip, any case, e.g. H100, H200 or A100 80GB.
fromNoFirst UTC day, YYYY-MM-DD (default: 29 days before `to`).

Output Schema

NameRequiredDescriptionDefault
toNo
chipNo
daysNo
fromNo
noteNo
unitNo
errorNoOnly on an error result: an object {code, message}, or the reason string of an x402 PaymentRequired object.
sourcesNo
count_daysNo
history_last_dayNo
history_first_dayNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changed
    • removedInput schema / properties / chip / title
      Removed value: -"Chip"
    • removedInput schema / properties / from / default
      Removed value: -null
    • removedInput schema / properties / from / title
      Removed value: -"From"
    • removedInput schema / properties / to / default
      Removed value: -null
    • removedInput schema / properties / to / title
      Removed value: -"To"
    • removedInput schema / title
      Removed value: -"get_gpu_price_indexArguments"
    • removedOutput schema / properties / days / items
      Removed value: -{
      -  "properties": {
      -    "akash": {
      -      "properties": {
      -        "gpus_available": {
      -          "type": [
      -            "integer",
      -            "null"
      -          ]
      -        },
      -        "gpus_total": {
      -          "type": [
      -            "integer",
      -            "null"
      -          ]
      -        },
      -        "max_usd": {
      -          "type": [
      -            "string",
      -            "null"
      -          ]
      -        },
      -        "median_usd": {
      -          "type": [
      -            "string",
      -            "null"
      -          ]
      -        },
      -        "min_usd": {
      -          "type": [
      -            "string",
      -            "null"
      -          ]
      -        },
      -        "read_at": {
      -          "type": [
      -            "string",
      -            "null"
      -          ]
      -        }
      -      },
      -      "type": [
      -        "object",
      -        "null"
      -      ]
      -    },
      -    "chip": {
      -      "type": [
      -        "string",
      -        "null"
      -      ]
      -    },
      -    "date": {
      -      "type": [
      -        "string",
      -        "null"
      -      ]
      -    },
      -    "generated_at": {
      -      "type": [
      -        "string",
      -        "null"
      -      ]
      -    },
      -    "lowest_on_demand_usd": {
      -      "type": [
      -        "string",
      -        "null"
      -      ]
      -    },
      -    "lowest_spot_usd": {
      -      "type": [
      -        "string",
      -        "null"
      -      ]
      -    },
      -    "median_on_demand_usd": {
      -      "type": [
      -        "string",
      -        "null"
      -      ]
      -    },
      -    "on_demand_offers": {
      -      "type": [
      -        "integer",
      -        "null"
      -      ]
      -    }
      -  },
      -  "type": [
      -    "object",
      -    "null"
      -  ]
      -}
    • removedOutput schema / properties / sources / items
      Removed value: -{
      -  "type": [
      -    "string",
      -    "null"
      -  ]
      -}
  2. Added

TDQS

A4/5.0
Behavior5/5

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

Adds substantial context beyond the annotations: data provenance (list prices and marketplace bids, not executed trades), gap semantics (missing days are not interpolated), typical latency under 0.1 s, per-call cost of USD 0.002, and a free quota of 10 calls per IP per UTC day. The read-only, idempotent, open-world traits are already covered by annotations, and nothing here conflicts with them.

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?

Front-loaded with the core verb and resource, then the returned fields, then caveats, then operational facts (latency, price, quota, docs). Nearly every sentence earns its place; the 'utilpeek:' vendor prefix is the only mildly redundant element.

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?

An output schema exists, so return values need no explanation; the description instead supplies the semantic framing an agent needs — what the prices represent, how gaps behave, and what calling costs. Nothing material is missing for a 3-parameter read-only lookup.

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?

Schema coverage is 100%, with from/to defaults and formats fully documented in the schema, so the baseline is 3. The description reinforces the chip dimension with concrete examples (H100, H200, A100) and explains that output is daily snapshots, which slightly informs the date-range meaning, but it adds no new syntax or constraint detail.

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?

States a specific verb and resource: returns a GPU chip's daily rental price history with named fields (lowest/median on-demand list price, spot, Akash median bid, free GPUs). The word 'history' implicitly separates it from a current-prices sibling like get_gpu_prices, but no sibling is named, so differentiation is inferred rather than stated.

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?

The description makes the usage context obvious (time-series rental pricing) and clarifies the data is list prices and marketplace bids rather than executed trades, which guides interpretation. However, it never says when to prefer this over export_gpu_price_history or get_gpu_prices, and gives no explicit exclusions.

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.