Skip to main content
Glama

rentgpu GPU rental price market data

platform_reliability

各 GPU 租用平台的数据监测覆盖度评分(A~E):自动抓取成功率、收录天数、库存充足率、覆盖卡型数。注意:衡量的是本数据源对该平台的价格监测覆盖度,不代表平台自身的服务质量。示例: platform_reliability() → 31 家平台评分,如 gpushare 99 分 A 级(抓取成功率 98%、覆盖 7 张卡、39/40 天)。按次计费 $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": "platform_reliability"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

No annotations are supplied, so the description carries the behavioral burden and does so well: it discloses per-call cost ($0.005 USDC), the expected result size (~31 platforms), and a concrete worked example with the exact response shape. It omits confirmation that the call is read-only and non-parameterized, though the 'platform_reliability()' signature implies that.

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 purpose is front-loaded in the first clause, followed by the component list, a caveat, a worked example, and pricing — each sentence adds information. Slightly dense with mixed content, but no filler.

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?

With no output schema, the description must convey return values, and the worked example (gpushare 99 points, grade A, 98% success, 7 cards, 39/40 days) does that effectively for a simple parameterless scoring tool. The grading scale boundaries (what separates A from B) are not spelled out, a minor residual gap.

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 tool takes zero parameters, and the description's empty-argument signature 'platform_reliability()' is consistent with the schema. Baseline 4 applies when there are no parameters to explain.

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 states a specific output: A–E coverage/reliability grades per GPU rental platform, broken into four named components (scrape success rate, days covered, stock sufficiency, card models covered). This is far more than a restatement of the name. It does not, however, contrast itself with siblings like ghpi_index or gpu_price, which is what would be needed for a 5.

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

Usage Guidelines2/5

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

There is no guidance on when to call this versus the other eleven tools. The '注意' sentence clarifies how to interpret the score (data-source coverage, not platform quality), which is useful framing, but it is not a when-to-use or when-not-to-use instruction, and no alternative is named.

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