Skip to main content
Glama

GPU Economy - cloud GPU prices

by io.github.laserodds21
OverviewDiscussionsAdmin

Current prices for one GPU

gpu_prices
Read-only

Current listed rental prices for one GPU model across providers, cheapest first, in USD per GPU-hour, each with the time it was read and the GPU Economy page that links its source. Live quotes only.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
gpuYesGPU id (h100-sxm, h200, b200, rtx-4090) or a name ("H100 SXM", "RTX 4090").
limitNoRows to return, cheapest first; default 10.
marketNoMarket to keep; default on_demand. "any" keeps spot, community, serverless and reserved too.
regionNoRates listed in US or EU regions, plus rates that name no region (a provider's rate everywhere); default any.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
gpuNo
noteNo
pageNo
gpu_idNo
marketNo
pricesNo
quotesNo
regionNo
cite_asYesHow to cite this answer: GPU Economy, the page, the data date.
attributionYes
data_updated_atYesNewest scrape behind the answer (ISO 8601).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • 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"
+]
  2. Changed2 schema fields changed
    • addedInput schema / properties / region
      Added value: +{
+  "description": "Rates listed in US or EU regions, plus rates that name no region (a provider's rate everywhere); default any.",
+  "enum": [
+    "any",
+    "US",
+    "EU"
+  ],
+  "type": "string"
+}
    • 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": {},
+    "market": {},
+    "note": {},
+    "page": {},
+    "prices": {},
+    "quotes": {},
+    "region": {}
+  },
+  "required": [
+    "data_updated_at",
+    "attribution"
+  ],
+  "type": "object"
+}
  3. Changed1 schema field changed
    • changedInput schema / properties / gpu / description
      Previous value: -"GPU id from list_gpus (h100-sxm, h200, b200, rtx-4090) or a name (\"H100 SXM\", \"RTX 4090\")."New value: +"GPU id (h100-sxm, h200, b200, rtx-4090) or a name (\"H100 SXM\", \"RTX 4090\")."
  4. First observed

TDQS

A4/5.0
Behavior4/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 goes further by disclosing the sort order (cheapest first), freshness ('Live quotes only'), and what each row carries (read time plus a source link), which is useful behavioral context beyond the structured fields.

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

Conciseness5/5

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

Two sentences, front-loaded with the resource and scope, no filler. Every clause (across providers, cheapest first, per GPU-hour, live only) carries information.

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?

An output schema exists, so return values need no further explanation, and the description covers scope, ordering, currency, and freshness. Only the when-to-use routing against sibling pricing tools is unaddressed.

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 all four parameters (gpu, limit, market, region) are already documented in the schema with defaults and enums. The description reinforces 'cheapest first' and 'USD per GPU-hour' but adds no syntax or format detail the schema lacks; baseline 3 applies.

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 resource (current listed rental prices for one GPU model) with scope details: across providers, cheapest first, USD per GPU-hour. This is specific enough that an agent can distinguish it from price_history (historical) and price_index without opening a 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?

'Live quotes only' implicitly excludes the history sibling, but the description never explicitly says when to use this versus provider_prices, compare_providers, or price_index. Usage context is implied rather than stated.

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 toolsInspect
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