Skip to main content
Glama

Import cluster

import_cluster
Destructive

Import an EXISTING Kubernetes cluster into Ankra - any distribution, any provider, anywhere (EKS, GKE, AKS, k3s, kind, on-premises). This is how a cluster that already runs is brought under Ankra management, and it is NOT the same as the create_*_cluster / create_managed_cluster tools, which provision brand-new billable cloud infrastructure. Use this one whenever the user says import, onboard, connect, add, or bring in a cluster they already have. Two steps by design: this call registers the cluster and returns import_command, the command that installs the Ankra Agent; the operator then runs it against that cluster's kubeconfig, because Ankra has no route into a cluster it has not met. The cluster reports 'offline' until the agent checks in. Only onboards NEW clusters - a name that already exists is refused rather than reconfigured. It does not connect a GitOps repository; use connect_gitops_repository afterwards for that.

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

Input Schema

NameRequiredDescriptionDefault
nameYesName the cluster gets in Ankra. Alphanumeric with dashes and underscores, and unique in the organisation - an existing name is refused, not overwritten.
descriptionNoOptional free-text description of what this cluster is for.
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 label stays empty, which every gate reads as production.

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 label stays empty, which every gate reads as production.",
      +  "enum": [
      +    "development",
      +    "staging",
      +    "testing",
      +    "production",
      +    "local"
      +  ],
      +  "type": "string"
      +}
  2. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, idempotentHint=false, and destructiveHint=true; the description goes further by disclosing the two-step design, that it returns import_command, that the cluster stays 'offline' until the agent checks in, and that an existing name is refused rather than reconfigured. It stops short of explaining what the destructiveHint actually entails at the cluster level (agent installation side effects), so a small gap remains.

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 purpose, then alternatives, then the two-step mechanics and constraints — a logical order. Several parenthetical lists (distributions, synonyms) are dense but each carries real disambiguation value; the text is long but not padded.

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?

With no output schema, the description still explains the key return value (import_command) and the post-call state ('offline' until the agent checks in), which is what an agent needs to report to the user. Non-idempotency, duplicate-name refusal, and the GitOps hand-off are all covered for a three-parameter mutation tool.

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 schema already documents name, description, and environment in detail, including the enum and the production-default behavior. The tool description adds no parameter-level meaning beyond that, so the baseline of 3 applies.

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 ('Import an EXISTING Kubernetes cluster into Ankra') and immediately delimits scope ('any distribution, any provider'). It explicitly distinguishes itself from create_*_cluster / create_managed_cluster, which provision new billable infrastructure, so an agent can separate the two without opening either schema.

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?

Gives explicit trigger vocabulary ('whenever the user says import, onboard, connect, add, or bring in a cluster they already have') and an explicit exclusion against the create_* family. It also names a downstream alternative, connect_gitops_repository, for the adjacent task it does not perform.

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.