GrabGPU

Find a GPU to rent

find_gpu

Read-onlyIdempotent

Find cloud GPUs to rent now: price per GPU hour and the stock each provider reported at the last hourly check. Rentable offers come first, cheapest first. Each offer has a rent_url that opens the provider (some are referral links, same price for the buyer).

Input Schema

TableJSON Schema

Name	Required	Description
`gpu`	No	GPU model, e.g. "H100", "B300", "RTX 4090". Omit for every model.
`limit`	No	How many offers, default 20, at most 100.
`in_stock`	No	Default true: only offers the provider reports in stock. false: also offers that are out of stock or have unknown stock, for a full market view.
`min_gpus`	No	Smallest node size needed, e.g. 8 for an 8x node.
`max_price`	No	Highest USD per GPU hour.

Output Schema

TableJSON Schema

Name	Required	Description
`unit`	Yes
`offers`	Yes
`captured_at`	Yes	When the prices and stock were collected

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 9, 2026

changedInput schema / properties / in_stock / description

Previous value: -"Only offers the provider reports in stock. Default true."New value: +"Default true: only offers the provider reports in stock. false: also offers that are out of stock or have unknown stock, for a full market view."

Changed7 schema fields changedOct 4, 2026

addedInput schema / properties / limit / maximum
```
Added value: +100
```
addedInput schema / properties / limit / minimum
```
Added value: +1
```

changedInput schema / properties / limit / type

Previous value: -"number"New value: +"integer"

addedInput schema / properties / max_price / exclusiveMinimum
```
Added value: +0
```
addedInput schema / properties / min_gpus / minimum
```
Added value: +1
```

changedInput schema / properties / min_gpus / type

Previous value: -"number"New value: +"integer"

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "captured_at": {
+      "description": "When the prices and stock were collected",
+      "type": "string"
+    },
+    "offers": {
+      "items": {
+        "properties": {
+          "availability": {
+            "enum": [
+              "in_stock",
+              "unknown",
+              "out_of_stock"
+            ],
+            "type": "string"
+          },
+          "country": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "direct_url": {
+            "type": "string"
+          },
+          "gpu": {
+            "description": "GPU slug, e.g. \"nvidia-h100\"",
+            "type": "string"
+          },
+          "gpu_count_range": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "gpu_name": {
+            "type": "string"
+          },
+          "is_referral": {
+            "description": "rent_url ends in a referral link; the buyer pays the same price",
+            "type": "boolean"
+          },
+          "max_gpus": {
+            "description": "Largest node the provider offers",
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "provider": {
+            "description": "Provider slug",
+            "type": "string"
+          },
+          "provider_name": {
+            "type": "string"
+          },
+          "rent_url": {
+            "description": "Link to give the buyer; counts the click, then opens the provider",
+            "type": "string"
+          },
+          "usd_per_gpu_hour": {
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "vram_gb": {
+            "type": [
+              "number",
+              "null"
+            ]
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "unit": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "captured_at",
+    "unit",
+    "offers"
+  ],
+  "type": "object"
+}

First observedSep 27, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Beyond the annotations (readOnly, idempotent, non-destructive), the description discloses result ordering (rentable offers first, cheapest first), stock freshness semantics, and that some rent_url links are referrals at the same price. These are exactly the behavioral details an agent cannot infer from 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?

Three tight sentences that front-load purpose, then ordering, then the rent_url caveat. Every sentence carries information an agent would otherwise have to guess.

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?

With a full output schema, complete parameter descriptions, and annotations covering the safety profile, the description fills the remaining gap (ordering, stock freshness, referral links). Nothing needed to invoke or interpret results 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 all five parameters (gpu, limit, in_stock, min_gpus, max_price) are already documented in the schema. The description adds no parameter-level syntax or format detail, so the 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 verb (Find) and resource (cloud GPUs to rent) and immediately clarifies the payload: price per GPU hour plus provider-reported stock. There are no siblings to differentiate from, and the scope (rentable GPUs) is unambiguous.

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?

Context is clear — this is for renting GPUs right now — and the description flags that stock reflects the last hourly check, which tells the agent how fresh the data is. With no sibling tools there is no alternative to route to, but there is no explicit when-not guidance either.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All GrabGPU 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?