Skip to main content
Glama

Import managed cluster

import_managed_cluster
Destructive

Adopt a managed Kubernetes cluster that already runs at the provider (the twin of ankra cluster managed import): Ankra fetches its kubeconfig through the provider API and installs the agent itself, so unlike import_cluster there is no command for the operator to run. Take provider_cluster_id from discover_managed_clusters. Refused when the cluster is already imported or the name is taken. The cluster reads as offline until the agent checks in.

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>",
      "credential_id": "<credential_id>",
      "provider_cluster_id": "<provider_cluster_id>"
    },
    "name": "import_managed_cluster"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoName the cluster gets in Ankra. Defaults to the provider's name.
providerYesManaged Kubernetes provider.
descriptionNoOptional 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.
credential_idYesUUID of the provider credential the cluster is reachable through.
provider_cluster_idYesThe provider's cluster id (from discover_managed_clusters).

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.3/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true and idempotentHint=false, and the description adds real behavior beyond them: Ankra pulls the kubeconfig through the provider API, installs the agent itself, and the cluster reports as offline until the agent checks in. What it does not explain is why the operation is marked destructive (what, if anything, is mutated or overwritten at the provider), which is the one gap for a destructive-flagged tool.

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-loads the purpose, then the sibling distinction, then the parameter source, then failure modes and post-call state — a sensible information order. It is dense with five clauses, but none is filler; the parenthetical CLI twin is the only mildly expendable piece.

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 mutation tool with no output schema, the description covers what the tool does to the outside world, where the ID comes from, what causes rejection, and the immediate post-call state. It leaves the destructive annotation unexplained, which is the main thing an agent still lacks before committing to the call.

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%, including the note that provider_cluster_id comes from discover_managed_clusters, so the description's sourcing hint largely repeats the schema. It adds no guidance on credential_id choice or on how name interacts with the 'name is taken' refusal. Baseline 3 is appropriate when the schema already documents all six parameters.

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 ('Adopt a managed Kubernetes cluster that already runs at the provider') and immediately differentiates it from the sibling import_cluster by noting there is no operator command to run. An agent can distinguish this from create_managed_cluster or import_cluster without opening any 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?

Explicitly routes the agent: use this when the cluster already exists at the provider, use import_cluster when an operator command is acceptable, and get provider_cluster_id from discover_managed_clusters. It also names the refusal conditions (already imported, name taken), which tells the agent when the call will fail rather than succeed.

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.