Skip to main content
Glama

rentgpu GPU rental price market data

market_movers

近 90 天 GPU 行情涨跌榜:按区间涨跌幅排序的降价/涨价卡型,含当前价与区间最低价。示例: market_movers(top=3) → 降价榜 A6000 48GB 2.52 元(-28.6%)、A100 80GB 5.47 元(-21.6%)、RTX 3090 0.80 元(-19.2%)。按次计费 $0.005 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": "market_movers"
  }
}

Input Schema

NameRequiredDescriptionDefault
topNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior3/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 useful traits: pay-per-call billing ($0.005 USDC), the 90-day window, the sort order, and the returned fields with a concrete sample output. However, it omits whether results are cached, whether the ranking can be inverted (降价 vs 涨价 is mentioned but not how to select it), and any freshness or data-source caveats.

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?

It is front-loaded with the scope and ordering, then a concrete example, then the price. Every sentence carries information; nothing is padding.

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 tool with no output schema and no annotations, the description covers return contents, ordering, time window, and cost, which is nearly everything needed to call it correctly. The remaining gap is how a caller requests the 涨价 (price-increase) list versus the 降价 list shown in the example.

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?

The single parameter `top` has 0% schema coverage (no type description beyond integer/default 5), but the example market_movers(top=3) → three listed entries effectively demonstrates that `top` is the count of ranked entries returned, which is genuine meaning added beyond the schema.

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 states a specific resource (近 90 天 GPU 行情涨跌榜) plus the ordering rule (按区间涨跌幅排序) and the returned fields (当前价、区间最低价). That makes it clearly distinct from siblings like gpu_price (single price) and gpu_history (time series) without needing to name them.

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 conveyed only implicitly through the worked example market_movers(top=3); there is no explicit statement of when to prefer this over gpu_history or gpu_price, and no exclusions. An agent can infer the use case (ranking movers) but must reason about alternatives itself.

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