Skip to main content
Glama

GPU Cloud

by ca.gpucloud
OverviewDiscussionsAdmin

Quote a server

gpucloud_quote_server
Read-only

Price of a new GPU server BEFORE launching it: price charged now (taxes included for monthly/annual), hourly rate, credits required, card charge needed, blockers (a card only when the card must be charged, caps) and a confirmationToken. Hourly: also the action at the threshold (onFundsExhausted, allowedOnFundsExhausted), the threshold (hibernationThresholdCad) and, when the automatic reload is off, autoReloadWarning (code AUTO_RELOAD_OFF, message to show the user, link to turn the reload on). Show the price and the warning to the user and get approval, then call gpucloud_create_server with the SAME arguments and the token. (permission: servers:quote) [Requires a free GPU Cloud account and MCP key]

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 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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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"
+}
  2. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already establish it is a safe read (readOnlyHint=true, destructiveHint=false), and the description goes well beyond them: it enumerates what the quote returns (price charged now with taxes for monthly/annual, hourly rate, credits required, card charge needed, blockers, confirmationToken) and discloses the single-use token dependency that gates the follow-up create call. That is real behavioral context an agent cannot get from the annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core purpose and the call-then-create workflow are front-loaded, and the dense field listing is largely justified by the absence of an output schema. It is slightly overstuffed with return-field names in one long sentence, which costs a point but not a major one.

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?

With no output schema, the description carries the full burden of describing what comes back, and it does so thoroughly: charge-now amount, hourly rate, credits, card charge, blockers, and the hourly-specific hibernation threshold and AUTO_RELOAD_OFF warning. An agent has everything it needs to present a quote and proceed to creation.

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 the schema already documents all eight parameters, including the cycle semantics and onFundsExhausted behavior. The description mirrors the hourly return fields but adds no new syntax, format, or constraint information about the inputs themselves, so the baseline 3 applies.

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?

States a specific verb and resource — 'Price of a new GPU server BEFORE launching it' — and immediately anchors the result to a concrete action (call gpucloud_create_server with the same arguments and token). This separates it from the sibling create tool and from the launching path without needing either schema opened.

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?

Gives an explicit workflow: show the price and warning to the user, get approval, then call gpucloud_create_server with the SAME arguments and the confirmationToken. It also names the prerequisites (free GPU Cloud account and MCP key) and the permission scope (servers:quote).

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

All GPU Cloud 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