paraloncloud-rentals
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PARALON_API_KEY | Yes | API key for ParalonCloud Rental API | |
| PARALON_BASE_URL | No | Base URL for the API (default: https://paraloncloud.com/api/v1) | https://paraloncloud.com/api/v1 |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_gpusA | List GPU nodes available to rent right now, with price per hour, GPU model, VRAM, CUDA compute capability, and country. Rent by the returned node_id. reserved_for_you: true marks a node its provider keeps for this key's person or organization: such nodes come first and nobody else sees them. Read-only, no cost. For modern LLM work prefer compute_cap >= 8.9 (FP8). |
| get_balanceA | Get the account's credit balance (rentals are billed per minute against it). Read-only, no cost. |
| create_rentalA | Start renting a GPU. SPENDS CREDITS (per-minute billing) — confirm with the user before calling. Asynchronous: returns a rental_id with status 'pending'. Provisioning + the secure tunnel take ~20-40 seconds. After creating, call get_rental ONCE to fetch the connection URL — it waits internally for startup and returns when ready, so do NOT poll it in a tight loop. DURATION: the rental is open-ended by default (runs until the user stops it with destroy_rental) — use open-ended as the default. When starting one, briefly tell the user it's open-ended and bills per minute until stopped, and that they can set an 'hours' auto-stop cap instead if they prefer; only pass 'hours' when the user asks for a time limit. An idempotency key is generated automatically so accidental repeats don't start a second GPU. |
| get_rentalA | Get one rental's status and connection details (Jupyter URL + token). After create_rental, call this to get the URL. It WAITS internally (up to ~24s) for the rental to finish coming up and returns as soon as it's ready — so you usually only need ONE call, at most two. Do NOT call it repeatedly in a tight loop. Provisioning plus the secure tunnel take ~20-40 seconds total; the URL is ready when connection_pending is false. Read-only. |
| list_rentalsA | List the account's rentals. By default only active ones (what's running and billing). Pass status='all' for full history. Read-only. |
| destroy_rentalA | Stop a rental — stops the GPU and STOPS BILLING. This is the money brake; safe to call twice. Confirm with the user unless they clearly asked to stop it. |
| list_my_nodesA | PROVIDER: list the GPU nodes this account provides (needs a key with the 'nodes' scope). For each node: state (available, rented, paused, not_verified, not_ready, offline), GPUs and VRAM, price (default, allowed min/max, custom, what a renter pays), verification, reputation, the current rental (never the renter), and live metrics from the last minute: per-GPU load %, temperature °C, power W and VRAM, plus host CPU and memory. Read-only. |
| get_my_nodeC | PROVIDER: one of the account's nodes, same fields as list_my_nodes (state, price, rental, live GPU metrics). Read-only. |
| add_nodeA | PROVIDER: add a new node to the account and get the docker command that installs the agent on the machine. Confirm the name and type with the user first. The returned command contains the node's secret token: show it only to the user, never paste it anywhere public. The node comes online once the command runs on the machine, then goes through the GPU check. At most 20 nodes an hour per key. |
| get_node_install_commandA | PROVIDER: the docker command that installs the agent for an existing node (to reinstall or move it). It contains the node's secret token: show it only to the user. Read-only. |
| set_node_availableA | PROVIDER: take a node off the market (available=false) or put it back (available=true). Off stops new rentals at once; a rental already running goes on to its end. Use it when the owner needs the machine or it is rented on another marketplace. Confirm with the user unless they asked for exactly this. |
| set_node_priceA | PROVIDER: set a node's price in US dollars per hour for the whole node (what the renter pays; the provider gets it minus the platform fee), or null to go back to the platform default. Must be within the node's price.min and price.max (50% to 300% of the default; see get_my_node). A rental already running keeps its price. Not possible on a spot node. Confirm the new price with the user first. |
| update_nodeA | PROVIDER: change several things on a node at once: name, spot (true/false; refused while the node is rented, and turning spot on clears a custom price), available, price_per_hour (USD per hour or null). Send only what changes. Confirm changes with the user first. |
| reclaim_spot_nodeA | PROVIDER: take a spot node back for the owner's own use ("In use"): rentals and inference go off, and a spot rental running on it STOPS TWO MINUTES LATER (the renter is told). Only for spot nodes. Always confirm with the user first. Put the node back afterwards with set_node_available(true). |
| get_node_accessC | PROVIDER: who can rent a node. An empty list (private: false) means everyone; otherwise only the people (email), email domains and organizations listed see the node and can rent it. Read-only. |
| set_node_accessA | PROVIDER: set who can rent a node, replacing the whole list. Each entry is {kind: "email", value: "ana@company.com"}, {kind: "domain", value: "company.com"} or {kind: "org", value: ""}. A non-empty list makes the node PRIVATE: only those renters see it and can rent it, and ParalonCloud places no inference or other work on it, so it earns from their rentals only. [] opens it to everyone again. Call get_node_access first to keep existing entries. Always confirm with the user first. People and organizations added are told by email. |
| get_earningsA | PROVIDER: the account's earnings in USD by UTC day for the last |
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 17 tools
Provider and renter operations are clearly separated, and each tool names a distinct resource+action. There is some overlap: update_node can also change 'available' and 'price_per_hour', which collides with set_node_available and set_node_price, and reclaim_spot_node overlaps with set_node_available(false) on spot nodes. The descriptions clarify the difference (batch vs. single-field, spot-specific semantics), so misselection is unlikely but not impossible.
All 17 tools follow a consistent verb_noun snake_case pattern (list_my_nodes, set_node_access, create_rental, destroy_rental). The role prefixes (my/rental/node) are used predictably, and read vs. write is obvious from the verb. Minor variation between add_node and create_rental is the only deviation and does not break the pattern.
17 tools is on the heavy side of the sweet spot but justified because the server serves two distinct roles (provider node management and renter GPU usage). Almost every tool maps to a real operation earning its place. It could be tightened if update_node absorbed the single-field setters.
The renter lifecycle (list_gpus, create_rental, get_rental, destroy_rental, list_rentals) and provider lifecycle (add, install command, get/list, price, availability, access, earnings) are well covered. Notable gaps: there is no way to remove/delete a node from the account once added, and no credit top-up or payout operation (payouts explicitly excluded). These are minor and documented, so agents can mostly work around them.