Skip to main content
Glama

Taipei Ledger

GPU rental prices

gpu_prices
Read-onlyIdempotent

GPU rental prices in US$ per GPU-hour from cloud providers and marketplaces (AWS, Azure, Google Cloud, Oracle, CoreWeave, Lambda, RunPod, Vast.ai and others), by model (e.g. 'H100 SXM', 'B200', 'RTX 4090') and price type. Without a model: the latest price per model and provider.

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
daysNo
modelNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

With readOnlyHint, idempotentHint and openWorldHint=false already supplied, the description still adds real value: currency, per-GPU-hour normalization, source coverage, and the default result granularity when no model is given. It stops short of saying what the returned records look like or how the time window shapes the result.

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 compact clauses, each earning its place: scope and units first, then the dimensions and sources, then the default behavior. No filler and no repetition of the title.

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?

For a simple read-only lookup with no output schema and two optional parameters, the description covers enough to call it correctly on the model axis and to understand the result granularity. The unaddressed `days` parameter and the exact shape of returned rows are the remaining gaps.

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 0%, so the description carries the full burden. It does well for `model`, giving concrete example values ('H100 SXM', 'B200', 'RTX 4090') and explaining the no-model fallback, but it never explains `days` (default 14) — whether it is a lookback window, an averaging period, or a filter — leaving one of two parameters opaque.

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?

The description names a specific resource (GPU rental prices), the unit and currency (US$ per GPU-hour), the data sources (AWS, Azure, Google Cloud, Oracle, CoreWeave, Lambda, RunPod, Vast.ai), and the dimensions of aggregation (model, provider, price type). None of the sibling tools touch hardware pricing, so this is immediately distinguishable.

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?

It describes one mode explicitly: without a model, the result is the latest price per model and provider. That is useful conditional guidance, but there is no statement of when an agent should reach for this tool or when a narrower query is preferable; usage is only implied by the subject matter.

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.

Resources