Skip to main content
Glama

rentgpu GPU rental price market data

recommend_for_task

按任务推荐最便宜的 GPU 租用方案:输入任务(如'微调 7B'/'视频生成',或英文 finetune-7b/video-gen),返回推荐卡型、最便宜平台、每小时单价与估算任务总成本。覆盖 8 类任务:微调、推理、绘图、视频、渲染、学生练手、70B 训练、多卡集群。示例: recommend_for_task(task='微调 7B') → 最便宜卡 + 平台 + 单价 × 8 小时的总成本。这是别处没有的'按任务问价'能力。按次计费 $0.01 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": {
      "task": "<task>"
    },
    "name": "recommend_for_task"
  }
}

Input Schema

NameRequiredDescriptionDefault
taskYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/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 does well: it discloses the return contents (recommended card, platform, unit price, estimated job total), and importantly the billing model — $0.01 USDC per call. It does not state auth requirements or latency, but for a read-only recommendation query the key behavioral facts (cost, output shape) are covered.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Purpose is front-loaded, but the description repeats the example twice (mid-text and again at the end) and includes promotional filler ('这是别处没有的'). Some sentences duplicate the return-value list rather than adding new information.

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, the description supplies the task vocabulary and the shape of the returned recommendation, which is enough to invoke it correctly. Minor gaps are the input string format edge cases and no note on failure behavior for unsupported tasks.

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 coverage is 0% and the single parameter has no schema description, but the description fully compensates: it gives bilingual example inputs, lists the 8 valid task categories, and shows a concrete call signature recommend_for_task(task='微调 7B'). Only the exact accepted string grammar remains slightly ambiguous.

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 verb and resource — recommending the cheapest GPU rental plan per task — and explicitly frames it as a per-task pricing capability distinct from the price-listing siblings like gpu_price and list_gpu_models. An agent can tell exactly what it returns (card type, cheapest platform, hourly price, estimated total cost).

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

Usage Guidelines4/5

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

It specifies the input shape (task names like '微调 7B' or finetune-7b) and enumerates the 8 supported task categories, which tells the agent when the tool is applicable. It claims the capability is unavailable elsewhere but does not explicitly state exclusion conditions versus gpu_price or gpu_history, so it stops short of full when/when-not guidance.

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