Skip to main content
Glama
Sign In

Feegate AI Agent data marketplace catalog & platform metrics

by org.feegate
OverviewDiscussionsAdmin

gpu-market.gpu_cheapest_entry

Ask "where is the cheapest place to rent a GPU today" — the 20 cheapest in-stock offers across all platforms and regions, with USD and CNY per hour. Entry tier. The full 168-offer board is $0.05.

[zh] 供应方资产「GPU 算力价格榜（跨平台实采）」按次计费 $0.005 USDC（或等值积分）。 入参：无。 [en] Vendor asset "GPU 算力价格榜（跨平台实采）". Paid per call: $0.005 USDC (or prepaid credits). Args: none. 付款/支付头在 MCP 请求头里带（X-Payment / X-Payment-Tx / Authorization: Bearer fg_…），不要放进参数。

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": "gpu-market.gpu_cheapest_entry"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/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 the important operational facts: per-call cost of $0.005 USDC (or credits), the fact that payment credentials go in MCP request headers (X-Payment / X-Payment-Tx / Bearer fg_…) rather than parameters, and that the result set is filtered to in-stock offers. It does not state refresh cadence or how an empty result is signaled, which keeps it short of a 5.

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?

The English lead is well front-loaded and earns its space. However, the payment block is stated three times over — once inline in the English prose and again in near-identical [zh] and [en] restatements — which pads a tool whose useful content is about two sentences.

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 zero-parameter, no-output-schema tool, the description covers what is returned (20 offers, platforms, regions, dual currency), what it costs, and how payment is transmitted — enough for an agent to call it correctly. Only the freshness/update semantics implied by 'today' remain unstated.

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?

There are zero parameters and the description confirms 'Args: none', which matches the empty input schema exactly. Baseline for a no-parameter tool is 4; nothing further needs explaining.

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 opening sentence gives a concrete verb-and-resource framing ('cheapest place to rent a GPU today') and specifies the exact output scope: the 20 cheapest in-stock offers across all platforms and regions, priced in USD and CNY per hour. It also positions itself as the 'entry tier' against a 168-offer full board, so an agent can infer it is the lightweight sibling of gpu-market.gpu_board without opening either schema.

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?

Usage context is clear — pick this when the question is 'where is the cheapest GPU right now' and a 20-row answer suffices. It signals the fuller alternative exists ('The full 168-offer board is $0.05') but does not name gpu-market.gpu_board explicitly, so the agent must map the price hint to a sibling name on its own.

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

All Feegate AI Agent data marketplace catalog & platform metrics toolsInspect
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