Skip to main content
Glama
RareCloudio

@rarecloudio/mcp-server

Official
by RareCloudio

deploy_service

Order and provision a new cloud service, charging your account. Requires explicit confirmation after cost approval.

Instructions

Deploy (order + provision) a new service and CHARGE the account. Requires scope services:write. Polymorphic: category selects the product family (cloud-vm | cloud-k8s | cloud-volume | cloud-loadbalancer | cloud-network | server | hosting | proxy | domain); category may be omitted and is then inferred from the catalog product. productId (alias plan) is the catalog SKU; the other fields depend on the family — discover them with get_product_details, list_catalog_listings, list_kubernetes_versions, list_regions, list_images. SPENDS MONEY: this places a real order and provisions billable infrastructure. You MUST pass confirm:true, and only after the user has approved the plan and its cost (preview cost with get_product_details).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoAlias for hostname.
planNoAlias for productId.
portNo
tagsNo
imageNoAlias for imageId.
poolsNo
vpcIdNo
addonsNo
regionNoRegion code (see list_regions).
sizeGbNo
sshKeyNoAlias for sshKeyId.
confirmYesSet to true to execute. This operation spends from your account balance and/or is irreversible; only pass true after the user has explicitly approved. Omit or false → the tool refuses and makes no API call.
imageIdNo
payWithNo
categoryNoProduct family; inferred from the SKU if omitted.
hostnameNo
sshKeyIdNo
productIdNoCatalog SKU / backend product id.
workerMaxNo
workerMinNo
k8sVersionNo
healthCheckNo
machineTypeNo
billingCycleNo
customFieldsNo
rootPasswordNo
sshPublicKeyNocloud-vm: raw public key injected via cloud-init.
configOptionsNo
memberServerIdsNo
Behavior5/5

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

Clearly warns that it spends money and provisions billable infrastructure. States that confirm:true is required for execution, otherwise no API call is made. Irreversibility implied. No annotations exist, so description carries full burden and does so well.

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

Conciseness5/5

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

Description is brief yet comprehensive: main purpose first, then behavioral warnings, then parameter guidance. Every sentence adds value. No fluff.

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?

Given the tool's complexity (29 params, polymorphic, billing), the description covers the essential workflow, prerequisites, cost implications, and parameter discovery. No output schema, so return value explanation is omitted appropriately.

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?

With only 31% schema description coverage, the description adds significant value by explaining polymorphic behavior (category selects family), aliases (name, plan, image, sshKey), and directing users to discover family-specific fields via other tools. However, it does not describe all 29 parameters individually.

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?

Clearly states it deploys a new service and charges the account. Distinguished from sibling tools like stop, destroy, etc. by focusing on ordering/provisioning.

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 requires scope services:write and user approval before passing confirm:true. Recommends previewing cost with get_product_details and discovering parameters with helper tools. Provides clear when-to-use and when-not-to-use guidance.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/RareCloudio/rarecloud-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server