GPU Economy - cloud GPU prices

Cloud GPU Price Index (H100)

price_index

Read-only

The Cloud GPU Price Index: median listed on-demand H100 SXM rate across providers, this week and the last eight weeks, with the base-100 index and the receipts; also the newest hourly point and the monthly averages over a fixed panel.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`window`	No	Which window leads the answer; default week. Every answer carries the newest value of each.

Output Schema

TableJSON Schema

Name	Required	Description
`hour`	No
`name`	No
`page`	No
`method`	No
`months`	No
`series`	No
`window`	No
`cite_as`	Yes	How to cite this answer: GPU Economy, the page, the data date.
`current`	No
`receipts`	No
`attribution`	Yes
`data_updated_at`	Yes	Newest scrape behind the answer (ISO 8601).

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 1, 2026

addedOutput schema / properties / cite_as

Added value: +{
+  "description": "How to cite this answer: GPU Economy, the page, the data date.",
+  "type": "string"
+}

changedOutput schema / required

Previous value: -[
-  "data_updated_at",
-  "attribution"
-]New value: +[
+  "data_updated_at",
+  "attribution",
+  "cite_as"
+]

Changed1 schema field changedOct 1, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "attribution": {
+      "type": "string"
+    },
+    "current": {},
+    "data_updated_at": {
+      "description": "Newest scrape behind the answer (ISO 8601).",
+      "type": "string"
+    },
+    "hour": {},
+    "method": {},
+    "months": {},
+    "name": {},
+    "page": {},
+    "receipts": {},
+    "series": {},
+    "window": {}
+  },
+  "required": [
+    "data_updated_at",
+    "attribution"
+  ],
+  "type": "object"
+}

Changed1 schema field changedOct 1, 2026

addedInput schema / properties / window

Added value: +{
+  "description": "Which window leads the answer; default week. Every answer carries the newest value of each.",
+  "enum": [
+    "week",
+    "hour",
+    "month"
+  ],
+  "type": "string"
+}

First observedSep 28, 2026

TDQS

B3.2/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds useful shape detail (fixed panel, base-100 index, receipts, monthly averages), but says nothing about provider coverage limits, how the fixed panel is composed, or freshness beyond 'newest hourly point'.

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?

A single compact sentence that front-loads the resource and headline metric. It is somewhat jargon-dense ('receipts', 'base-100 index') but wastes no sentences and nothing is buried.

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 an output schema present, return-value detail is not the description's burden, and the one optional enum param is fully documented in schema. For a zero-required-parameter read tool the description is nearly complete, only missing sibling routing.

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 description coverage is 100% and the enum values week/hour/month are documented in the schema, including the 'which window leads the answer' behavior. The description adds nothing parameter-specific, so the baseline 3 applies.

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 resource and scope: median listed on-demand H100 SXM rate across providers, this week plus eight prior weeks, with the base-100 index and monthly averages. This clearly separates it from gpu_prices and price_history, though it reads more as a content inventory than an action statement.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No explicit when-to-use or when-not-to-use guidance. The description never mentions gpu_prices, price_history, or provider_prices, so the agent must infer that this is the H100-specific index view rather than a general price lookup. The 'window' default is the only steering signal, and that lives in the schema.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All GPU Economy - cloud GPU prices tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?