Skip to main content
Glama

rentgpu GPU rental price market data

gpu_price

查某张 GPU 现在的全平台最低价(元/小时),含报价平台、区间最低/最高/均价(最多 90 天)、当前价与区间最低价的差距。示例: gpu_price(gpu='RTX 4090') → 当前最低 1.24 元/小时(算家云)、市场中位 1.99、区间最低 1.24、今日 8 家报价。按次计费 $0.002 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_price"
  }
}

Input Schema

NameRequiredDescriptionDefault
gpuYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does disclose several behavioral facts: the per-call cost ($0.002 USDC), the 90-day maximum lookback window for the range statistics, and the shape of the returned data. It omits failure behavior, e.g. whether an unrecognized GPU string returns an empty result or an error, which matters for a free-form string key.

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?

One dense sentence covering scope and return fields, front-loaded with the core purpose, followed by a concrete example. No filler, and the cost note is a single clause at the end.

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 one-parameter read tool with no output schema and no annotations, the description supplies the output shape, the data window, and the price. The remaining gap is valid-input guidance and error semantics, which are minor but non-trivial for a free-text lookup key.

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% and the single `gpu` parameter has no schema-level documentation. The example (gpu='RTX 4090') teaches the expected value format, which is real added meaning, but the description never says whether matching is exact or fuzzy or that list_gpu_models can supply valid names.

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?

States a specific verb and resource ("查某张 GPU 现在的全平台最低价") plus the exact returned fields: quoting platform, range min/max/average over up to 90 days, and the gap between current and range-minimum price. The time-scoped wording ("现在") implicitly separates it from gpu_history, but no sibling is named explicitly, so differentiation is left to inference.

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?

Usage is only implied by the temporal qualifier "现在的" (current snapshot, not a time series). There is no explicit statement about when to prefer gpu_history or bulk_snapshot_query, and no guidance on what to do when a GPU name is unknown or ambiguous. The worked example partially compensates by showing a successful call.

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