rentgpu GPU rental price market data

bulk_snapshot_query

从逐日原始快照里按条件筛报价：指定若干日期 + 卡型/平台，返回命中的原始报价（含计费说明口径、来源、抓取时间），按价格升序。示例: bulk_snapshot_query(dates='latest', gpu='昇腾910B2 64GB')。快照原文免费：https://rentgpu.link/data/snapshots/<日期>.json ；此处计费的是跨多天筛选与聚合。按次计费 $0.02 USDC。

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": "bulk_snapshot_query"
  }
}

Input Schema

Name	Required	Default
`gpu`	No
`dates`	No	latest
`limit`	No
`platform`	No

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 2, 2026

TDQS

A4.9/5.0

Behavior5/5

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

With no annotations, the description must carry the behavioral load. It successfully discloses critical traits: the returned fields (billing details, source, capture time), the sorting mechanism (price ascending), and the operational cost ($0.02 USDC per call).

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 description is extremely dense and packed with vital information (function, output, cost, usage, example), making it highly efficient. It is perhaps slightly dense, but every element contributes essential context.

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?

Given the complexity of historical data querying, filtering, and the implication of external costs and links, the definition is nearly complete. An agent has all necessary context to decide whether to call it, what parameters to use, and what the result will entail.

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

Parameters5/5

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

Since the schema description coverage is 0%, the description must add all semantic meaning. It clarifies that 'dates' allows for specifying multiple days and defines the input types conceptually (GPU, platform, dates). The example usage reinforces these meanings.

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 clearly defines the action (filtering/screening quotes), the source (daily raw snapshots), and the scope (date + card type/platform). It is highly specific and easy to distinguish from other potential tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides a crucial usage guideline by contrasting this paid service with the free raw snapshot data, explicitly telling the agent when to choose this tool versus checking the provided URL. The included example further clarifies usage.

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

All rentgpu GPU rental price market data 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?