Skip to main content
Glama

List managed Kubernetes options

list_managed_k8s_options
Read-only

List managed-Kubernetes provisioning options; two folded modes. Without a cluster target: what a provider credential can reach for creating a NEW managed cluster (locations, Kubernetes versions, node sizes, zones, private networks, cluster plans, capabilities) - credential_id is required (ankracloud_k8s falls back to the organisation's built-in Ankra Cloud credential). With cluster_id or cluster_name: an EXISTING managed cluster's region-filtered options plus its available Kubernetes upgrades (current version and upgrade candidates). 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). Read-only; talks to the cloud provider's API, so it can take a few seconds.

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": "list_managed_k8s_options"
  }
}

Input Schema

NameRequiredDescriptionDefault
providerYesManaged Kubernetes provider.
cluster_idNoUUID of an existing managed cluster to list options and upgrades for.
cluster_nameNoExact name of an existing managed cluster to list options and upgrades for.
credential_idNoUUID of the provider credential. Required for the creation catalogue (no cluster target), except for ankracloud_k8s, where an omitted credential_id uses the organisation's built-in Ankra Cloud credential; ignored when a cluster is targeted.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations only declare readOnlyHint, and the description adds real behaviour: confirmation that it is read-only, an explicit latency warning because it calls the cloud provider's API, and per-provider availability gating (kapsule requires Scaleway enabled, ankracloud_k8s requires Ankra Cloud enabled). It does not discuss pagination or response shape beyond field enumeration, but with no output schema and only a single annotation the added context is substantial.

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?

Front-loaded with the verb and the two-mode split, then dense supporting detail; every clause carries information (mode selection, credential rules, provider mapping, latency). It is a single long run-on paragraph with a trailing provider enumeration, which slightly hurts scannability but nothing is truly padding.

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?

With no output schema, the description carries the return-value burden and largely discharges it by enumerating the catalogues returned in each mode (locations, versions, node sizes, zones, private networks, cluster plans, capabilities, upgrade candidates). Minor gaps remain: what happens if both cluster_id and cluster_name are supplied, and which wins is left to inference.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds genuine meaning the schema lacks: it maps each opaque enum value to a cloud (eks=AWS, aks=Azure, gke=GCP, doks=DigitalOcean, uks=UpCloud, ovh_mks=OVH, kapsule=Scaleway, ankracloud_k8s=Ankra Cloud). That provider glossary is the main ambiguity an agent would otherwise hit.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Names a specific verb and resource ("List managed-Kubernetes provisioning options") and immediately disambiguates the two folded modes by their inputs (no cluster target vs cluster_id/cluster_name). It does not route against the crowded field of neighbouring option-listing tools (list_kubernetes_versions, list_instance_types, list_proxmox_options, list_upcloud_options, discover_managed_clusters), so an agent must infer the boundary from the 'managed-Kubernetes' qualifier alone.

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?

Explicitly states the condition that selects each mode: absence of a cluster target means the creation catalogue, presence of cluster_id or cluster_name means existing-cluster options plus upgrades. It also gives the credential prerequisite per mode and the ankracloud_k8s fallback. No exclusions or named alternatives are offered, so it stops short of full when-not guidance.

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.