Skip to main content
Glama

Launch a server (spends money)

gpucloud_create_server

Launches a GPU server billed to the account. Requires the confirmationToken of gpucloud_quote_server for exactly these arguments and the key caps. Neither a card nor the automatic reload is required when the credits pay the first hour; the saved card is charged (and then needed) only for missing credits (at least $25, or the automatic reload amount when larger) or a monthly / annual order. Without enough funds (no credit and no usable card, or a cap reached) it returns a tool error with httpStatus 402 and accountAction (code PAYMENT_REQUIRED; BUDGET_CAP_REACHED for a cap) carrying the message and the console link to fix it; the quote itself never carries a payment link. Hourly: the answer carries onFundsExhausted and, when the automatic reload is off, autoReloadWarning. The owner receives an email for every spend. [SPENDS MONEY] (permission: servers:create) [Requires a free GPU Cloud account and MCP key]

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": {
      "productId": "<productId>",
      "sshKeyId": "<sshKeyId>",
      "confirmationToken": "<confirmationToken>"
    },
    "name": "gpucloud_create_server"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoDisplay name of the server.
cycleNohourly: first hour from credits, then billed per hour. monthly / annual: first month charged to the saved card.hourly
regionNoRegion id (gpucloud_list_regions), default canada-montreal.canada-montreal
sshKeyIdYesSSH key id (gpucloud_list_ssh_keys).
productIdYesGPU product id (gpucloud_list_products).
templateIdNoOptional one-click template installed at creation (gpucloud_list_templates): jupyter, ollama-openwebui, vllm, comfyui, pytorch.
templateModelNoModel served by the vllm template (gpucloud_list_templates models[].id); default: the first one.
onFundsExhaustedNoHourly servers: what happens when the balance runs short and no automatic reload brings it back. HIBERNATE (default): hibernated at its threshold (its GPU place is kept, hourly hibernation fee), restarted as soon as the balance is back. DELETE: no hibernation fee, kept running while the balance pays its next hour, then stopped. Machines that cannot be hibernated (spot) are always DELETE. A server is never deleted while the account has credit left. When the balance covers only about 24 hours of what the account spends per hour, a first notice is sent while the servers still run, then two more about 24 hours and 1 hour before the deletion; a server is deleted with its data only once it is out of service (stopped or hibernated for lack of credit, or hibernated by the user for at least 72 hours), once the credit is exhausted (the balance no longer pays the next hour of the account's servers), after the three notices and at least 24 hours after the first. Adding credits cancels the deletion.
confirmationTokenYesToken returned by the previous (quote) call, valid 10 minutes, single use.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / onFundsExhausted / description
      Previous value: -"Hourly servers: what happens when the balance reaches the server threshold and no automatic reload brings it back. HIBERNATE (default): hibernated (its GPU place is kept, hourly hibernation fee), restarted as soon as the balance is back, deleted after 12 h without credit. DELETE: deleted at once, no hibernation fee, data lost. Machines that cannot be hibernated (spot) are always DELETE."New value: +"Hourly servers: what happens when the balance runs short and no automatic reload brings it back. HIBERNATE (default): hibernated at its threshold (its GPU place is kept, hourly hibernation fee), restarted as soon as the balance is back. DELETE: no hibernation fee, kept running while the balance pays its next hour, then stopped. Machines that cannot be hibernated (spot) are always DELETE. A server is never deleted while the account has credit left. When the balance covers only about 24 hours of what the account spends per hour, a first notice is sent while the servers still run, then two more about 24 hours and 1 hour before the deletion; a server is deleted with its data only once it is out of service (stopped or hibernated for lack of credit, or hibernated by the user for at least 72 hours), once the credit is exhausted (the balance no longer pays the next hour of the account's servers), after the three notices and at least 24 hours after the first. Adding credits cancels the deletion."
  2. Changed1 schema field changed
    • addedInput schema / properties / onFundsExhausted
      Added value: +{
      +  "description": "Hourly servers: what happens when the balance reaches the server threshold and no automatic reload brings it back. HIBERNATE (default): hibernated (its GPU place is kept, hourly hibernation fee), restarted as soon as the balance is back, deleted after 12 h without credit. DELETE: deleted at once, no hibernation fee, data lost. Machines that cannot be hibernated (spot) are always DELETE.",
      +  "enum": [
      +    "HIBERNATE",
      +    "DELETE"
      +  ],
      +  "type": "string"
      +}
  3. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations only declare the generic safety profile (not read-only, not idempotent, open-world), while the description adds substantial context: error shape with httpStatus 402, accountAction codes PAYMENT_REQUIRED and BUDGET_CAP_REACHED, console link, and owner email on every spend. It stops short of stating rate limits or quota behavior beyond the budget cap, so it is rich but not exhaustive.

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 first two sentences are front-loaded and high value, but the long narrative about deletion notices, hibernation windows, and the 24-hour/1-hour warnings largely restates the onFundsExhausted schema description verbatim in spirit. That bulk is redundant for an agent that already reads the schema and pushes the description toward a wall of prose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, and the description compensates by naming the returned fields (onFundsExhausted, autoReloadWarning), the error envelope, and the permission scope servers:create. An agent has enough to call this correctly and to interpret both success and payment failure.

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?

Schema coverage is 100%, so the baseline is 3; the description earns one more by adding a real constraint not in the schema — the token is bound to 'exactly these arguments' — which tells the agent the token cannot be reused with modified parameters. Most other parameter meaning (cycle billing, onFundsExhausted) is already carried by the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Opens with a specific verb and resource plus the billing consequence: 'Launches a GPU server billed to the account.' The title reinforces the money-spending nature, and the required confirmationToken from gpucloud_quote_server distinguishes it from quote/list siblings in one clause.

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

Usage Guidelines5/5

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

Explicitly states the prerequisite flow (a prior gpucloud_quote_server call with exactly these arguments) and the conditions under which a card is or is not needed, including the monthly/annual exception. The failure conditions (no credit and no usable card, or cap reached) tell the agent when the call will not succeed.

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