DAP Compute Market Tracker

Current GPU rental price

get-gpu-price

Read-only

Use when you need what one cloud charges to rent a GPU in one region now. Returns the price per GPU-hour, the last change, the source URL and when it was read. 50 free calls a day, then $0.01 USDC on Base per call via x402.

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": {
      "chip": "<chip>",
      "provider": "<provider>",
      "region": "<region>"
    },
    "name": "get-gpu-price"
  }
}

Input Schema

Name	Required	Description	Default
`chip`	Yes	GPU family, for example H100, A100, H200, B200, B300 or GB200.
`region`	Yes	One region, by code or name, for example us-east-1, eastus or East US.
`provider`	Yes	Cloud provider: AWS or Azure.
`price_type`	No	On-demand (default) or Spot.	on-demand

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 4, 2026

TDQS

A4/5.0

Behavior4/5

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

The annotations already mark it read-only and closed-world, while the description adds useful behavior beyond schema: it returns source URL and read time, and it discloses the free-call limit plus x402 payment after 50 daily calls. Error handling is not described, but the rate-limit and cost context are substantive.

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?

Three tight sentences cover the use case, return contents, and cost/rate limit. The structure is front-loaded and no sentence feels redundant.

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 four-parameter price lookup with full schema coverage, read-only annotations, and no output schema, the description supplies the key return fields and pricing model. The main omission is sibling differentiation, which affects tool selection more than correct invocation.

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 100%, so chip, provider, region, and price_type are fully documented in the schema. The description adds no parameter-specific examples or constraints beyond saying 'one cloud' and 'one region', so the baseline 3 is appropriate.

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 retrieval: the current price to rent a GPU from one cloud in one region now, including price per GPU-hour and last change. It is clear what the tool returns, but it does not explicitly distinguish itself from siblings such as find-cheapest-gpu-hour or compute_list_prices.

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 gives an explicit use condition: 'Use when you need what one cloud charges to rent a GPU in one region now.' That clearly frames the intended context, but it does not state when not to use it or name alternatives for lowest-price or price-history queries.

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

All DAP Compute Market Tracker tools Inspect

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

Need Help?