GPU Economy - cloud GPU prices

Weekly price history of one GPU

price_history

Read-only

Weekly median and cheapest listed on-demand rate for one GPU model, newest week first, from two sources kept apart: our own hourly reads, and a series reconstructed from a public price catalog (second-hand). Each week carries its panel size; read a median against it.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`gpu`	Yes	GPU id or name.
`weeks`	No	Weeks per source, newest first; default 12.

Output Schema

TableJSON Schema

Name	Required	Description
`gpu`	No
`note`	No
`page`	No
`gpu_id`	No
`series`	No
`cite_as`	Yes	How to cite this answer: GPU Economy, the page, the data date.
`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"
+    },
+    "data_updated_at": {
+      "description": "Newest scrape behind the answer (ISO 8601).",
+      "type": "string"
+    },
+    "gpu": {},
+    "gpu_id": {},
+    "note": {},
+    "page": {},
+    "series": {}
+  },
+  "required": [
+    "data_updated_at",
+    "attribution"
+  ],
+  "type": "object"
+}

AddedOct 1, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=true, openWorldHint=false), and the description adds real context beyond them: results are newest-week-first, the two sources are kept separate rather than blended, one series is a reconstructed second-hand catalog, and each week carries a panel size. It does not discuss rate limits or caching, but the provenance disclosure is genuinely useful.

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 dense sentences, front-loaded with what the tool returns and from which sources. The closing clause 'read a median against it' is terse to the point of being cryptic, but nothing is wasted.

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?

A read-only query tool with a full output schema, so return-shape explanation is not required, yet the description usefully explains that medians/cheapest values are per-week and per-source with a panel size. Nothing essential for correct invocation is missing; only the alternative-tool routing is absent.

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%, so both params (gpu, weeks) are already documented, including the default of 12 and the newest-first ordering. The description repeats the newest-first framing but adds no syntax or format detail beyond the schema, so baseline 3 applies. The 'read a median against it' note guides interpretation rather than parameter meaning.

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 specific verb and resource: weekly median and cheapest listed on-demand rate for one GPU model. It also names the two distinct sources (own hourly reads vs. a reconstructed public-catalog second-hand series), which sharply separates it from siblings like gpu_prices, price_index, and recent_price_changes.

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?

Usage is implied (this is the tool for weekly historical rates for a single GPU), but the description never says when to prefer it over siblings such as recent_price_changes or price_index, nor any exclusions. The agent must infer routing from the phrasing alone.

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?