Skip to main content
Glama

Create UpCloud cluster

create_upcloud_cluster
Destructive

Create and provision a new Kubernetes cluster on UpCloud. Requires an UpCloud API credential, SSH key credential, and a zone. The cluster will begin provisioning immediately after creation. Use list_provider_credentials to find credential IDs and list_instance_types for plan sizes.

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": {
      "name": "<name>",
      "credential_id": "<credential_id>",
      "ssh_key_credential_id": "<ssh_key_credential_id>",
      "zone": "<zone>"
    },
    "name": "create_upcloud_cluster"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesCluster name. Must be unique within the organisation.
zoneYesUpCloud zone (e.g., 'de-fra1', 'fi-hel1', 'nl-ams1', 'us-chi1').
zonesNoZone pool for a multi-zone cluster; must include 'zone' (the primary). Needs at least 3 zones and 3 control planes; the nodes are joined by a platform-managed WireGuard mesh. Omit for a single-zone cluster.
descriptionNoOptional cluster description.
environmentNoWhat the cluster is for. Ankra's autonomy gates treat a cluster like production until a person confirms what it is for. A label named here is that confirmation only when a member confirms this call's card in Ankra chat; over MCP, or with no member's confirmation, it is recorded as set by automation and confirms nothing (a production label is still honoured). Omit it and the cluster is labelled development, recorded as a default nobody confirmed.
gateway_apiNoAlso serve the Kubernetes Gateway API: the cluster's Traefik serves Gateway API routes (HTTPRoute) next to Ingress, and Ingress keeps working. Adds the Gateway API CRDs, a shared traefik-gateway Gateway in the traefik namespace (a plain HTTP listener that accepts routes from every namespace), and cert-manager and external-dns support for those routes. Needs the networking stack (on by default): asking for it with include_networking=false is refused. Default: false. Set at create only; no tool turns it on or off on an existing cluster.
worker_planNoUpCloud plan for worker nodes. Default: 'PREMIUM-2xCPU-4GB'.
bastion_planNoUpCloud plan for the bastion host. Default: 'STARTER-1xCPU-1GB'.
distributionNoKubernetes distribution. Default: 'kubeadm' (vanilla upstream Kubernetes with Cilium). 'k3s' is the lightweight alternative.
gateway_planNoUpCloud NAT gateway plan every node's outbound internet runs through. Default: 'standard' (500 Mbps, two servers). A plan with server_number 1 ('development', 'essentials') cuts all cluster egress while UpCloud rebuilds its one server; two-server plans fail over. Get the plans from list_upcloud_options (gateway_plans).
network_modeNoDerived when omitted: 'wireguard_mesh' for a multi-zone pool, 'private_network' otherwise. 'wireguard_mesh' on a single zone makes the cluster mesh-capable.
worker_countNoNumber of worker nodes. Default: 1.
credential_idYesUUID of the UpCloud API credential. Get from list_provider_credentials with provider='upcloud'.
control_plane_planNoUpCloud plan for control plane nodes. Default: 'PREMIUM-4xCPU-8GB'.
kubernetes_versionNoVersion for the chosen distribution. With the default distribution (kubeadm) pass a plain upstream tag such as v1.36.4, from list_kubernetes_versions with engine 'kubeadm'. With distribution 'k3s' pass a k3s build such as v1.35.7+k3s1, from engine 'k3s' (a bare patch resolves to its newest +k3sN build). A +k3sN build without distribution 'k3s' is refused. Omit it to install the catalogue's stable version for the distribution.
control_plane_countNoNumber of control plane nodes. Default: 1.
ssh_key_credential_idYesUUID of the SSH key credential. Get from list_provider_credentials with provider='ssh-key'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / control_plane_plan / description
      Previous value: -"UpCloud plan for control plane nodes. Default: 'PREMIUM-2xCPU-4GB'."New value: +"UpCloud plan for control plane nodes. Default: 'PREMIUM-4xCPU-8GB'."
  2. Changed1 schema field changed
    • addedInput schema / properties / environment
      Added value: +{
      +  "description": "What the cluster is for. Ankra's autonomy gates treat a cluster like production until a person confirms what it is for. A label named here is that confirmation only when a member confirms this call's card in Ankra chat; over MCP, or with no member's confirmation, it is recorded as set by automation and confirms nothing (a production label is still honoured). Omit it and the cluster is labelled development, recorded as a default nobody confirmed.",
      +  "enum": [
      +    "development",
      +    "staging",
      +    "testing",
      +    "production",
      +    "local"
      +  ],
      +  "type": "string"
      +}
  3. Changed1 schema field changed
    • addedInput schema / properties / gateway_api
      Added value: +{
      +  "description": "Also serve the Kubernetes Gateway API: the cluster's Traefik serves Gateway API routes (HTTPRoute) next to Ingress, and Ingress keeps working. Adds the Gateway API CRDs, a shared traefik-gateway Gateway in the traefik namespace (a plain HTTP listener that accepts routes from every namespace), and cert-manager and external-dns support for those routes. Needs the networking stack (on by default): asking for it with include_networking=false is refused. Default: false. Set at create only; no tool turns it on or off on an existing cluster.",
      +  "type": "boolean"
      +}
  4. Changed1 schema field changed
    • addedInput schema / properties / gateway_plan
      Added value: +{
      +  "description": "UpCloud NAT gateway plan every node's outbound internet runs through. Default: 'standard' (500 Mbps, two servers). A plan with server_number 1 ('development', 'essentials') cuts all cluster egress while UpCloud rebuilds its one server; two-server plans fail over. Get the plans from list_upcloud_options (gateway_plans).",
      +  "type": "string"
      +}
  5. First observed

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true and idempotentHint=false, and the description adds genuinely useful context that provisioning starts immediately on creation, implying it is not a draft. It still says nothing about cost implications, expected provisioning duration, or what a partially failed create leaves behind, which matters for a non-idempotent mutating call.

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?

Three lean sentences: what it does, what it needs, what happens next, then where to get the inputs. Nothing is repeated from the schema and no sentence is filler.

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

Completeness3/5

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

For a 17-parameter, non-idempotent cluster-creation call with no output schema, the description omits what is returned (cluster ID, provisioning status) and how to track progress after creation. The heavy parameter surface is well documented in the schema, but the post-call story is a real gap.

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?

With 100% schema description coverage across all 17 parameters, the schema already carries the semantics, including defaults, enums, zone-pool constraints and the gateway_api behaviour. The description only restates that credential, SSH key and zone are needed, adding no meaning beyond the schema, so 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?

Names a specific verb and resource (create and provision a Kubernetes cluster) and pins the provider (UpCloud), which distinguishes it cleanly from the many sibling create_*_cluster tools for AWS, Hetzner, DigitalOcean and others. An agent can select it without opening the schema.

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

Usage Guidelines4/5

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

States prerequisites (UpCloud API credential, SSH key credential, a zone) and routes the agent to list_provider_credentials and list_instance_types for the values it needs. It stops short of explicit when-not-to-use guidance or comparing itself to create_managed_cluster / create_cluster_mesh, so 4 rather than 5.

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.