Skip to main content
Glama

Create Morpheus cluster

create_morpheus_cluster
Destructive

Create and provision a new Kubernetes cluster on HPE Morpheus. Requires an HPE Morpheus credential, an SSH key credential, and the numeric Morpheus placement ids (group, cloud, network, layout) plus service-plan ids for the bastion, control plane, and workers. Use list_morpheus_options to resolve every id. The cluster will begin provisioning 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": {
      "name": "<name>",
      "credential_id": "<credential_id>",
      "ssh_key_credential_id": "<ssh_key_credential_id>",
      "group_id": "<group_id>",
      "cloud_id": "<cloud_id>",
      "network_id": "<network_id>",
      "layout_id": "<layout_id>",
      "bastion_plan_id": "<bastion_plan_id>",
      "control_plane_plan_id": "<control_plane_plan_id>",
      "worker_plan_id": "<worker_plan_id>"
    },
    "name": "create_morpheus_cluster"
  }
}

Input Schema

NameRequiredDescriptionDefault
cniNoCluster CNI. Default: 'cilium' when the distribution is kubeadm (the default distribution), 'flannel' when it is k3s. The kubeadm install sets up cilium only.
nameYesCluster name. Must be unique within the organisation.
cloud_idYesMorpheus cloud id (from list_morpheus_options).
group_idYesMorpheus group id (from list_morpheus_options).
layout_idYesMorpheus instance layout id (from list_morpheus_options).
network_idYesMorpheus network id (from list_morpheus_options).
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.
node_groupsNoOptional heterogeneous worker pools. When provided, worker_count and worker_plan_id are ignored. Each entry creates `count` workers on the given service plan with the given labels and taints.
distributionNoKubernetes distribution. Default: 'kubeadm'.
etcd_plan_idNoOptional service-plan id for external etcd nodes. Falls back to control_plane_plan_id.
worker_countNoNumber of worker nodes when node_groups is not provided. Must be at least 1 unless node_groups is supplied. Default: 1.
credential_idYesUUID of the HPE Morpheus credential.
etcd_topologyNoetcd topology. 'external' requires distribution 'kubeadm'. Default: 'stacked'.
worker_plan_idYesService-plan id for worker nodes (from list_morpheus_options).
bastion_plan_idYesService-plan id for the bastion VM (from list_morpheus_options).
etcd_node_countNoNumber of external etcd nodes (3 or 5). Only used when etcd_topology is 'external'. Default: 3.
virtual_image_idNoOptional Morpheus virtual image id to clone the VMs from.
include_networkingNoPublish the Ankra networking stack after bootstrap (disables the k3s-bundled Traefik). Default: true.
kubernetes_versionNoKubernetes version. If not specified, uses the latest stable version.
control_plane_countNoNumber of control plane nodes (1 or 3 for HA). Default: 1.
control_plane_plan_idYesService-plan id for control plane nodes (from list_morpheus_options).
ssh_key_credential_idYesUUID of the SSH key credential to authorise on the cluster servers.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / cni / description
      Previous value: -"Cluster CNI. Default: 'flannel'."New value: +"Cluster CNI. Default: 'cilium' when the distribution is kubeadm (the default distribution), 'flannel' when it is k3s. The kubeadm install sets up cilium only."
  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. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare destructive=true, readOnly=false and non-idempotent, so the safety profile is covered. The description adds meaningful context beyond that: provisioning starts immediately after confirmation and no ids can be guessed, which tells the agent this is irreversible up-front work.

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?

Three sentences, front-loaded with the action, then prerequisites, then the immediacy warning. The id enumeration is long but earns its place as a checklist of what must be resolved first.

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 24-parameter, non-idempotent provisioning tool with no output schema, the description covers the essentials: prerequisites, id sourcing, and the fact that provisioning is triggered at call time. Failure/rollback behavior and what the call returns are left unstated, which is the main remaining 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?

Schema coverage is 100% with detailed per-parameter descriptions, so the schema carries the parameter burden. The description contributes a useful resolution pattern by grouping the ids into credential, placement and service-plan categories and directing to list_morpheus_options, but adds no semantics the schema lacks.

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') scoped to a named provider (HPE Morpheus), which separates it cleanly from the many provider-specific siblings such as create_aws_cluster and create_proxmox_cluster.

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 clear preconditions (HPE Morpheus credential, SSH key credential, numeric placement and service-plan ids) and points to list_morpheus_options as the resolver for every id. It stops short of explicitly naming the alternative cluster-creation tools or stating when a different cluster type should be chosen.

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.