Skip to main content
Glama

Order service

order_service
Destructive

Order a new VPS on VPSnet: request a quote, verify the exact EUR total and billing period, then confirm balance payment to provision the server.

Instructions

Order a new VPS. Requires sufficient account balance for balance payment. Payment object for balance: { payment: 1, successUrl: '', cancelUrl: '' }. First call returns confirmationRequired and an exact gross EUR quote without charging. Show the amount and billing period, obtain explicit approval, then call again with the unchanged order configuration and idempotencyKey, returned quoteToken, expected_total_eur and acknowledge_charge=true. The API key must have paid scope/caps enabled. Never replace the key after an uncertain payment; inspect that original attempt in the VPSnet panel. Quotes are retained in this MCP process; after a restart inspect the original attempt in the panel rather than submitting another order. Payment acceptance is not server readiness. Poll get_service for the returned order number. stateProcess.waitingReason=public_ip_inventory resumes the same paid CREATE automatically when inventory returns; do not place or pay for another order. stateProcess.attention=true needs operator attention. Follow follow_up for the same service. Poll about every 10 seconds, never treating that interval as a boot ETA; after at most 6 checks report pending progress and retain the original key/order. Do not automatically restart or promise a completion callback. Running VM, usable guest access and application health are separate checks. Resources: array of numeric resource value IDs from get_order_options, e.g. [901, 907]. rootPassword: 6-40 chars, alphanumeric, must contain uppercase + lowercase + digit. Example: 'MyPass123'. sshKey and rootPassword are mutually exclusive — provide one or the other. privateNetworkId (optional): the UUID of one of your private networks to attach the new server to at order time, the same choice the order form offers; the server checks the network in the quote and refuses the order with a reason when it cannot be attached. Omit it for an order without a private network.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
osNoOS version ID from get_order_options
planYesPlan ID from get_order_plans
periodYesExplicit billing period ID from get_order_options; disclose its term together with the exact gross quote before approval.
sshKeyNoSSH key ID from list_ssh_keys to deploy. Mutually exclusive with rootPassword
paymentYesPayment object. For balance: { payment: 1, successUrl: '', cancelUrl: '' }
resourcesNoArray of numeric resource value IDs from get_order_options, e.g. [901, 907, 902]
quoteTokenNoExact token returned by the first order_service call; required for confirmation.
rootPasswordNoRoot password. 6-40 chars, alphanumeric, must contain uppercase + lowercase + digit. Mutually exclusive with sshKey
idempotencyKeyYesRequired for paid API-key orders. Stable unique key for this exact order attempt, e.g. UUID.
privateNetworkIdNoUUID of one of your private networks to attach the new server to (shown in the control panel under Networking). Sent to both the quote and the confirm; omit for no private network
acknowledge_chargeNoSet only after explicit approval of the exact gross EUR total and billing period.
expected_total_eurNoExact VAT-inclusive amount_eur disclosed to and approved by the customer; required for confirmation.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.3.16

TDQS

A4.7/5.0
Behavior5/5

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

Annotations only declare destructiveHint=true and readOnlyHint=false; the description adds the crucial operational traits — the first call is non-charging, idempotency and key-retention rules, API-key scope requirements, quote lifetime tied to MCP process restarts, waitingReason/attention semantics, and the fact that payment acceptance is not server readiness.

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?

Front-loaded and justified in length for a paid two-phase order tool, but it restates schema text nearly verbatim for resources, rootPassword and privateNetworkId, and lines like "Follow follow_up for the same service." are opaque. The operational section earns its place; the schema echo does not.

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, yet the description explains the return surfaces an agent must handle: confirmationRequired and the gross EUR quote on the first call, the returned order number to poll, and stateProcess fields (waitingReason, attention). Polling cadence and the 6-check reporting ceiling are also specified.

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 schema already carries each parameter. The description still adds workflow-level meaning the schema cannot: which fields belong to the first (quote) call versus the second (confirm) call, and how quoteToken/expected_total_eur/acknowledge_charge must be carried over unchanged.

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 precise verb+resource statement, "Order a new VPS," which immediately separates it from the quote_/order_network_product and order_certificate siblings. The scope (new VPS provisioning with payment) is unambiguous.

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 explicit when/when-not guidance: first call returns a quote and charges nothing, then approval, then a second call with quoteToken/expected_total_eur/acknowledge_charge=true. It also names the alternatives and follow-up paths (poll get_service, follow follow_up, inspect the panel instead of retrying) and states conditions that must not trigger a re-order.

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

Deploy Server

Other Tools