Skip to main content
Glama

Create managed cluster

create_managed_cluster
Destructive

Create and provision a new MANAGED Kubernetes cluster - the cloud provider operates the control plane. Providers: eks (AWS), aks (Azure), gke (GCP), doks (DigitalOcean), uks (UpCloud), ovh_mks (OVH), kapsule (Scaleway; only for organisations with Scaleway enabled), ankracloud_k8s (Ankra Cloud Kubernetes; only for organisations with Ankra Cloud enabled); this is the ONLY way to create clusters on AWS, Azure, or GCP. Requires a provider credential (optional for ankracloud_k8s, which uses the organisation's built-in Ankra Cloud credential), a location slug, and at least one node pool ({name, size, count}); use list_managed_k8s_options first to resolve locations, versions, and node sizes. Optional: kubernetes_version, ha (DOKS only), cluster_plan (UKS only), kapsule.private_network_id (required for Kapsule). The cluster begins provisioning at the provider immediately after confirmation.

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": {
      "provider": "<provider>",
      "name": "<name>",
      "location": "<location>",
      "node_pools": "<node_pools>"
    },
    "name": "create_managed_cluster"
  }
}

Input Schema

NameRequiredDescriptionDefault
haNoHigh-availability control plane. DOKS only.
aksNoAzure options, only with provider aks: resource group, network plugin, SKU tier, private cluster, VNet subnet and maintenance window.
nameYesCluster name. Must be unique within the organisation.
kapsuleNoKapsule-only networking options; required when provider is 'kapsule'.
locationYesProvider location slug (region or zone, from list_managed_k8s_options).
providerYesManaged Kubernetes provider.
node_poolsYesWorker node pools. Each entry creates `count` nodes of the given provider `size` slug.
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.
cluster_planNoCluster plan slug. UKS only.
credential_idNoUUID of the provider credential. Get from list_credentials. Optional for ankracloud_k8s: omitted, the organisation's built-in Ankra Cloud credential is used.
ankracloud_k8sNoAnkra Cloud Kubernetes-only networking options; every member optional.
kubernetes_versionNoKubernetes version (from list_managed_k8s_options). If not specified, uses the provider default.

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. First observed

TDQS

A4.6/5.0
Behavior4/5

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

The description goes beyond annotations by defining the operational model (provider operates the control plane), the immediate behavioral consequence of calling the tool (provisioning begins immediately), and unique behavioral constraints for certain providers (e.g., Kapsule exclusivity). The `destructiveHint: true` annotation complements this behavioral safety warning.

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 description is dense due to the complexity of the multi-provider architecture, but it is highly efficient. Every sentence serves to define the scope, constraints, or required workflow, ensuring zero wasted words despite its length.

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 extreme complexity of managing Kubernetes clusters across multiple cloud providers, this definition is remarkably complete. It covers providers, requirements, prerequisites, optional constraints, and behavioral implications, leaving almost nothing for the agent to infer before making a well-informed choice.

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?

Even with 100% schema coverage, the description is highly semantic. It adds vital context for parameter usage, such as requiring 'at least one node pool' with specific internal requirements ({name, size, count}), and clarifies that certain fields are only conditional based on the selected provider, like `ha` (DOKS only).

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 clearly states the purpose (create and provision a MANAGED Kubernetes cluster) and explicitly lists all supported providers (eks, aks, gke, doks, etc.). It also defines its unique scope by noting it is the ONLY way to create clusters on major cloud providers like AWS, Azure, or GCP.

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 provides exhaustive usage guidelines, including prerequisites like needing a provider credential and a location slug. It also gives specific workflow instructions, advising the agent to use list_managed_k8s_options to resolve versions and sizes, and details when specific options are required (e.g., DOKS or UKS specific fields).

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.