Skip to main content
Glama

GPU Economy - cloud GPU prices

by io.github.laserodds21
OverviewDiscussionsAdmin

Current prices at one provider

provider_prices
Read-only

Every current listed rental price at one provider (runpod, lambda, aws, vast-ai, ...), in USD per GPU-hour, each with its read time and the GPU Economy page that links its source. Live quotes only.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
providerYesProvider id (runpod, lambda, coreweave, aws, azure, gcp, vast-ai) or its name.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNo
pricesNo
quotesNo
cite_asYesHow to cite this answer: GPU Economy, the page, the data date.
providerNo
attributionYes
provider_idNo
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. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "attribution": {
+      "type": "string"
+    },
+    "data_updated_at": {
+      "description": "Newest scrape behind the answer (ISO 8601).",
+      "type": "string"
+    },
+    "page": {},
+    "prices": {},
+    "provider": {},
+    "provider_id": {},
+    "quotes": {}
+  },
+  "required": [
+    "data_updated_at",
+    "attribution"
+  ],
+  "type": "object"
+}
  3. First observed

TDQS

A3.8/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 the safety profile is covered. The description adds real behavioral detail beyond that: the currency/unit (USD per GPU-hour), that each record carries a read time and a source-linking GPU Economy page, and that only live quotes are returned.

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 front-loaded sentence plus a short qualifier; the key scope ('at one provider') and unit arrive first. The parenthetical provider list is slightly redundant with the schema but stays compact.

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 the description need not detail return values, and it still summarizes what each record contains (price, read time, source page). Combined with the 100% covered single parameter and clear read-only annotations, nothing needed to invoke the tool correctly is missing.

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 the single provider parameter is already fully documented in the schema, including the id/name distinction and examples. The description echoes the same provider examples without adding new syntax or formatting guidance, so baseline 3 is appropriate.

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+resource (current listed rental prices) and a clear scope constraint ('at one provider'), and the USD per GPU-hour unit anchors what a price means. It implicitly distinguishes itself from price_history and recent_price_changes via 'current' and 'Live quotes only', though it never names those siblings outright.

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 rather than stated: the agent can infer this is the tool for enumerating all listed quotes for a single provider. There is no explicit when-to-use guidance against compare_providers, gpu_prices, or price_history, and no stated exclusions beyond 'Live quotes only'.

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