Skip to main content
Glama

rentgpu GPU rental price market data

gpu_history

查某张 GPU 过去最多 90 天每日价格序列:每日全平台最低价、当日市场中位价、最低价来自哪个平台、库存状态、当日报价家数。示例: gpu_history(gpu='H100 80GB', limit=7) → 2026-10-20 最低 8.28 元(paperspace)、中位 23.04、有货、9 家报价。按次计费 $0.02 USDC。

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "gpu": "<gpu>"
    },
    "name": "gpu_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
gpuYes
limitNo

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 no annotations, the description carries the burden and adds useful context: it is a read-style query, capped at 90 days, returns specific daily fields, and charges $0.02 USDC per call. It still does not state authentication needs, rate limits, or pagination behavior.

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?

The description is front-loaded with the core action and scope, followed by a concrete example and pricing. Dense but well-structured, with no irrelevant wording.

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?

The tool has no output schema and only two parameters, and the description explains the returned daily fields, the maximum range, an example result, and the per-call fee. That is sufficient for an agent to call it correctly.

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 description coverage is 0%, so the description must define parameters, and it does provide an example GPU value and shows limit=7 producing a 7-day series. It could more explicitly state that limit is a number of days and mention the default, but the meaning is inferable.

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?

The description clearly states a specific verb and resource: query one GPU's daily price series over up to 90 days. It also enumerates the output fields, so an agent can distinguish it from a simple current-price lookup, though it does not explicitly name sibling tools.

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?

The 90-day maximum and the example with limit=7 imply when this historical-series tool is appropriate. However, it does not explicitly say when to use gpu_price, bulk_export_series, or other siblings instead.

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