Skip to main content
Glama

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]

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>"
    },
    "name": "gpucloud_quote_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.

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.7/5.0
Behavior5/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=false, but the description goes well beyond them: it discloses the permission scope (servers:quote), the prerequisite of a free GPU Cloud account and MCP key, the blocker semantics (a card only when one must be charged, caps), and the hourly-only extras (onFundsExhausted action, hibernationThresholdCad, autoReloadWarning with code AUTO_RELOAD_OFF). The token handoff also implicitly explains the non-idempotent annotation.

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 most important facts — price before launch, what is returned, and the quote-then-create handoff — are front-loaded, and the parenthetical permission/account note is properly demoted to the end. It is a dense run-on with some nested parentheticals that slow parsing, but no sentence is filler.

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?

With no output schema, the description correctly enumerates the return payload, including the conditional hourly fields and the auto-reload warning, which an agent must surface to the user. The main remaining gap is token validity/expiry and what to do if the quote is stale, which matters for a non-idempotent quote-then-create flow.

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 description coverage is 100%, so the baseline is 3, but the description adds real invocation meaning: the quote must be called with the SAME arguments later passed to gpucloud_create_server, and it clarifies that onFundsExhausted/threshold behavior surfaces in the hourly quote. It does not, however, clarify the token's lifetime or whether arguments must match exactly at create time, which would have pushed it to a 5.

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?

The description opens with a specific verb and resource — pricing a new GPU server before launch — and immediately enumerates what the price response contains (charged-now price, hourly rate, credits, card charge, blockers, confirmationToken). That distinguishes it from gpucloud_create_server (which actually launches) and from gpucloud_quote_order (orders, not servers) without the agent needing to open a schema.

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?

It gives an explicit workflow: show the price and warning to the user, get approval, then call gpucloud_create_server with the SAME arguments plus the token. The alternative is named and the condition that selects it is stated, so the sequencing between quote and create is unambiguous.

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