spotgpu-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SPOTGPU_API_KEY | Yes | Your SpotGPU API key (sk_… from https://spotgpu-api.fly.dev). Required. | |
| SPOTGPU_BASE_URL | No | Base URL for the SpotGPU API. | https://spotgpu-api.fly.dev |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| spot_priceA | Get SpotGPU spot rental prices (best + alts) for a GPU type. Returns JSON from GET /v1/spot including best.usd_per_hr (upstream provider rental price, not a SpotGPU fee). Credits are for API calls, not GPU rental. Args: gpu: GPU type, e.g. RTX_4090, RTX_3090, RTX_A6000 qty: Number of GPUs (>= 1). Default 1. markets: Comma-separated markets. Default "vast,runpod". fresh: If true, bypass cache (query fresh=1). Default false. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
With only a single tool in the set, there is nothing to confuse it with; an agent cannot misselect between alternatives. Its purpose (fetch spot rental prices) is unambiguous.
The lone name spot_price is clear lowercase snake_case, matching the convention used by the parameters (gpu, qty, markets, fresh). There is no cross-tool inconsistency to evaluate, though it is a noun phrase rather than a verb_noun action name.
A one-tool surface is very thin even for a narrowly scoped pricing service; common companion needs (listing supported GPU types, markets, or making a booking) are absent. It works only for the single exact lookup it was built for.
The domain (GPU spot rental) realistically includes discovering GPU types/markets and possibly reserving capacity, none of which exist here. An agent can retrieve prices but hits a dead end for anything else, with no fallback operations.