Skip to main content
Glama

GPU rental prices

gpu_prices
Read-onlyIdempotent

What renting a GPU costs per hour. Without arguments: every GPU model with its on-demand range across providers. With a gpu id: every provider, kind (on demand, spot, reserved, marketplace) and machine, cheapest first, each with its source. Prices in mainland China (Alibaba Cloud) come separately, in CNY, with stock per zone. USD per GPU-hour, list and market prices as published, not invoices. A provider that sells whole machines is divided by the machine's GPU count, so its figure includes the CPUs and memory of the machine. Spot, reserved and marketplace prices are different products from on-demand. A price does not say the GPU is in stock. Not purchasing advice.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "gpu_prices"
  }
}

Input Schema

NameRequiredDescriptionDefault
gpuNoGPU id: b300, b200, h200, h100, a100-80gb, l40s, rtx-5090, rtx-4090, l20, a10, v100-32gb, v100, t4
kindNoRestrict to one kind of price

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior5/5

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

Beyond the readOnly/closed-world annotations, it discloses real behavioral traits: China (Alibaba Cloud) prices are returned separately in CNY with stock per zone, while everything else is USD per GPU-hour; list and market prices are 'as published, not invoices'; whole-machine sellers are divided by GPU count so their figure bundles CPU/memory; and spot/reserved/marketplace are explicitly different products from on-demand. It even disclaims that the data is not purchasing advice.

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?

The purpose is front-loaded in the first sentence and the two modes follow immediately, so an agent can stop reading early. It is long and caveat-heavy, with a few trailing sentences ('Not purchasing advice', stock caveat) that could be merged, but nearly every sentence carries distinct 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?

There is no output schema, so the description must convey the return shape itself, and it largely does: per-model ranges, per-provider/kind/machine entries ordered cheapest first, each with source, plus a separate CNY/stock-per-zone section. Currency and unit semantics (USD per GPU-hour) are covered, though the exact response structure and whether zone stock is nested are left implicit.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds genuine meaning: passing a gpu id expands the result to every provider, kind and machine with its source, and the kind alternatives are paraphrased in prose ('on demand, spot, reserved, marketplace') reinforcing the enum. It does not add format or accepted-value detail beyond the schema's own enumerated id list, so it is not a full 5.

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?

"What renting a GPU costs per hour" states a concrete verb (cost lookup) and resource (GPU rental), then splits the behavior into two modes: no arguments (per-model on-demand range across providers) versus a gpu id (per-provider/per-kind detail). It is unambiguous what the tool reports, though it never names a sibling (e.g. cheapest, estimate_cost) to draw the boundary against.

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?

The two invocation modes are spelled out explicitly: 'Without arguments: every GPU model with its on-demand range' and 'With a gpu id: every provider, kind ... cheapest first'. It also gives a useful caveat-driven usage cue ('A price does not say the GPU is in stock'). It stops short of telling the agent when to prefer a sibling tool over this one, so no exclusions are stated.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.