Skip to main content
Glama

Create DigitalOcean cluster

create_digitalocean_cluster
Destructive

Create and provision a new Kubernetes cluster on DigitalOcean. Requires a DigitalOcean API credential, SSH key credential, and a region. The cluster will begin provisioning immediately after creation. Use list_provider_credentials to find credential IDs; sizes are DigitalOcean droplet size slugs (e.g. 's-2vcpu-4gb') - list_instance_types does not cover DigitalOcean.

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>",
      "region": "<region>"
    },
    "name": "create_digitalocean_cluster"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesCluster name. Must be unique within the organisation.
regionYesDigitalOcean region slug (e.g., 'nyc3', 'ams3', 'fra1', 'sfo3').
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_sizeNoDigitalOcean droplet size for worker nodes. Default: 's-2vcpu-4gb'.
bastion_sizeNoDigitalOcean droplet size for the bastion host. Default: 's-1vcpu-1gb'.
distributionNoKubernetes distribution. Default: 'kubeadm' (vanilla upstream Kubernetes with Cilium). 'k3s' is the lightweight alternative.
worker_countNoNumber of worker nodes. Default: 1.
credential_idYesUUID of the DigitalOcean API credential. Get from list_provider_credentials with provider='digitalocean'.
control_plane_sizeNoDigitalOcean droplet size for control plane nodes. Default: 's-2vcpu-4gb'.
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
    • 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"
      +}
  2. 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"
      +}
  3. 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 readOnlyHint=false, idempotentHint=false and destructiveHint=true, so the safety profile is covered. The description adds one genuinely useful behavioral fact: 'The cluster will begin provisioning immediately after creation', signalling an irreversible, billable side effect that starts without a further confirm step. It says nothing about expected provisioning duration, cancellation, or how to check progress afterwards, so the addition is real but thin.

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?

Four short sentences, front-loaded with the action and prerequisites before the lookup hints. Every sentence carries information, though the size-slug example partially duplicates the worker_size/control_plane_size property descriptions.

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?

For a 14-parameter, non-idempotent provisioning tool with no output schema, the description covers the essentials: what is created, what is required, and that provisioning starts immediately. It would be stronger if it said what the call returns (cluster ID/handle) or which tool to poll for provisioning status, since no output schema exists to answer that.

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 baseline is 3. The description's parameter-related content (droplet size slugs, credential lookup via list_provider_credentials) largely restates what the schema already documents per-property, adding only the cross-tool pointer and the warning that list_instance_types will not return valid slugs.

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 ('Create and provision a new Kubernetes cluster') and pins the provider to DigitalOcean, which cleanly separates it from the many sibling create_*_cluster tools (aws, hetzner, ovh, proxmox, scaleway, upcloud, etc.). An agent can pick this over create_managed_cluster or create_aws_cluster without opening any 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?

Gives concrete prerequisites (DigitalOcean API credential, SSH key credential, region) and routes the agent to list_provider_credentials for credential IDs. It also prevents a likely wrong turn by stating that sizes are DigitalOcean droplet slugs and that list_instance_types does not cover DigitalOcean. It stops short of stating when not to use this tool (e.g. importing an existing cluster via import_cluster), so not a 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.