GPU Economy - cloud GPU prices

Recent price changes

recent_price_changes

Read-only

Listed prices that changed in the last 30 days, one row per quote, newest change first: the figure before its first change in the window, the figure now, and how many times it changed. A quote back at its starting figure is left out, and so are marketplace floors unless asked for. Optionally for one GPU or one provider.

Input Schema

TableJSON Schema

Name	Required	Description
`gpu`	No	Optional GPU id or name.
`limit`	No	Rows; default 20.
`provider`	No	Optional provider id or name.
`include_marketplaces`	No	Also list marketplace floors (Vast.ai), which move with every read; default false.

Output Schema

TableJSON Schema

Name	Required	Description
`page`	No
`window`	No
`changes`	No
`cite_as`	Yes	How to cite this answer: GPU Economy, the page, the data date.
`attribution`	Yes
`marketplaces`	No
`quotes_changed`	No
`data_updated_at`	Yes	Newest scrape behind the answer (ISO 8601).
`changes_in_window`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 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"
+}

addedOutput schema / properties / page
```
Added value: +{}
```

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"
+    },
+    "changes": {},
+    "changes_in_window": {},
+    "data_updated_at": {
+      "description": "Newest scrape behind the answer (ISO 8601).",
+      "type": "string"
+    },
+    "marketplaces": {},
+    "quotes_changed": {},
+    "window": {}
+  },
+  "required": [
+    "data_updated_at",
+    "attribution"
+  ],
+  "type": "object"
+}

First observedSep 28, 2026

TDQS

A4.2/5.0

Behavior5/5

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

Annotations already mark this read-only and closed-world, and the description adds substantive behavior on top: the 30-day window, newest-change-first ordering, omission of quotes that returned to their starting figure, and the fact that marketplace floors move on every read (which is why they're opt-in). That volatility note is exactly the kind of context annotations cannot convey.

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?

One dense, front-loaded sentence leads with the resource and window, then the row shape, then exclusions. Tight with no filler, though the packed clause chain makes it slightly heavy to parse.

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-value explanation is unnecessary, and the description still covers scope, ordering, and exclusions. Combined with the read-only annotation and full schema coverage, an agent has everything needed to call it correctly.

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% and every parameter is self-documented, so the schema already carries the load. The description reinforces the opt-in nature of marketplace floors and the filtering role of gpu/provider, but adds no new syntax, format, or default detail beyond the schema.

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?

Names a specific resource (listed prices that changed in the last 30 days) with the exact row granularity, ordering, and contents of each row. Exclusions and scope limits are stated, so an agent can distinguish it from price_history or price_index without reading the schema.

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?

It says results can optionally be narrowed 'for one GPU or one provider,' implying how the params are used, and states two exclusion conditions. But it never says when to pick this over price_history/price_index, nor names an alternative for full history or un-changed prices.

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?