GPU Economy - cloud GPU prices

Compare two providers

compare_providers

Read-only

Two providers on every GPU both list on-demand today: each side's cheapest on-demand rate card, the difference and which is lower, and the count. Community capacity and marketplace floors are left out of the comparison. Live quotes only.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`a`	Yes	First provider id or name (runpod, lambda, "Google Cloud").
`b`	Yes	Second provider id or name.

Output Schema

TableJSON Schema

Name	Required	Description
`a`	No
`b`	No
`gpus`	No
`note`	No
`page`	No
`cite_as`	Yes	How to cite this answer: GPU Economy, the page, the data date.
`lower_on`	No
`attribution`	Yes
`gpus_compared`	No
`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": {
+    "a": {},
+    "attribution": {
+      "type": "string"
+    },
+    "b": {},
+    "data_updated_at": {
+      "description": "Newest scrape behind the answer (ISO 8601).",
+      "type": "string"
+    },
+    "gpus": {},
+    "gpus_compared": {},
+    "lower_on": {},
+    "note": {},
+    "page": {}
+  },
+  "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 carry readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds meaningful context beyond annotations: the comparison is restricted to on-demand live quotes and deliberately omits community capacity and marketplace floors, which shapes what results mean.

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 what the comparison produces, then scope exclusions and the live-quote constraint. Dense but every clause carries information; the enumerated return fields are slightly run-on.

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 not be re-explained, and the description nonetheless frames them. Combined with the scope exclusions and short schemas, an agent has enough to invoke it correctly, with only sibling routing left implicit.

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 a and b are already documented including examples (runpod, lambda, "Google Cloud"). The description adds no parameter-level detail, 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 verb (compare) and resource (two providers) and enumerates what the result contains: each side's cheapest on-demand rate card, the difference, which is lower, and the count. It is clearly distinguishable in spirit from compare_gpus, though it never names that sibling to sharpen the boundary.

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

Usage Guidelines4/5

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

Gives clear scope context: on-demand only, live quotes only, and explicitly excludes community capacity and marketplace floors. That tells the agent when this tool applies and when to look elsewhere, though it names no alternative tool by name.

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?