Skip to main content
Glama

Create Scaleway cluster

create_scaleway_cluster
Destructive

Create and provision a new self-hosted Kubernetes cluster on Scaleway Instances. Requires a Scaleway credential, SSH key credential, region, and zone. Creates a new private network by default; pass private_network_id to attach an existing one. The default public gateway type is 'VPC-GW-S'. Use list_provider_credentials to find credential IDs and list_instance_types with provider='scaleway' for instance sizes (e.g. 'DEV1-M', 'GP1-S'). Kapsule (managed) creation remains available in the portal and CLI. Only available to organisations with Scaleway enabled.

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>",
      "zone": "<zone>"
    },
    "name": "create_scaleway_cluster"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesCluster name. Must be unique within the organisation.
zoneYesScaleway zone within the region (e.g., 'fr-par-1', 'nl-ams-1').
regionYesScaleway region (e.g., 'fr-par', 'nl-ams', 'pl-waw').
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_typeNoInstance type for worker nodes. Default: 'DEV1-M'.
bastion_portNoManaged bastion SSH port on the gateway: 1024-59999, or exactly 61000. Default: 61000.
distributionNoKubernetes distribution. Default: 'kubeadm' (vanilla upstream Kubernetes with Cilium). 'k3s' is the lightweight alternative.
gateway_typeNoScaleway VPC public gateway type (e.g., 'VPC-GW-S', 'VPC-GW-M'). Default: 'VPC-GW-S'.
worker_countNoNumber of worker nodes. Default: 1.
credential_idYesUUID of the Scaleway API credential. Get from list_provider_credentials with provider='scaleway'.
network_ip_rangeNoOptional CIDR for the new private network (e.g., '10.64.0.0/20').
retention_policyNoStorage retention on teardown. Default: 'retain'.
control_plane_typeNoInstance type for control plane nodes. Default: 'DEV1-M'.
kubernetes_versionNoKubernetes version. If not specified, uses the latest supported version.
private_network_idNoExisting Scaleway private network ID to attach; omit to create a new private network.
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. Added
  4. Removed
  5. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=false, so the safety profile is covered; the description adds useful side effects the schema does not surface, notably that a new private network is created by default and what the default gateway type is. It does not state that provisioning is long-running, whether the call blocks, or that resources are billable, which would be valuable for a create-and-provision operation.

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?

Six tight sentences, front-loaded with the action and prerequisites before defaults and the alternative path. Minor waste: the 'VPC-GW-S' default and the instance-size examples duplicate schema text verbatim, so a sentence or clause could be trimmed without loss.

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 19-parameter provisioning tool with no output schema, the description covers prerequisites, credential discovery, network behavior, defaults, and the managed-cluster alternative. What remains unaddressed is operational expectation: expected provisioning duration, whether the call returns immediately with a cluster ID, and failure/rollback behavior.

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 parameter meaning is already fully documented, including defaults, enums, and min/max bounds. The description adds little beyond the schema: it restates the private_network_id behavior and the 'VPC-GW-S' gateway default, and contributes only instance-size examples ('DEV1-M', 'GP1-S') that the schema also lists. Baseline 3 is appropriate.

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 first sentence states a specific verb and resource ('Create and provision a new self-hosted Kubernetes cluster on Scaleway Instances'), and explicitly scopes it to Scaleway Instances so it is distinguishable from create_aws_cluster, create_hetzner_cluster, create_managed_cluster, and the Kapsule path. The closing sentence notes that managed (Kapsule) creation is not offered by this tool, removing ambiguity with sibling creators.

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 names the required inputs (Scaleway credential, SSH key credential, region, zone), routes the agent to list_provider_credentials and list_instance_types with the right provider argument to obtain them, and states when to pass private_network_id versus letting a network be created. It also states the eligibility gate ('Only available to organisations with Scaleway enabled') and points to portal/CLI for the managed alternative.

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.