Skip to main content
Glama

Discover managed clusters

discover_managed_clusters
Read-only

List the managed Kubernetes clusters that already run in the provider account behind a credential (the twin of ankra cluster managed discover), marking the ones Ankra has already imported: name, location, version, status, node count and node pools. Providers: doks, uks, gke, aks, eks, ovh_mks, kapsule, ankracloud_k8s. Use this before import_managed_cluster; list_managed_k8s_options is the catalogue for creating NEW clusters, not this. Read-only; talks to the provider 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>",
      "credential_id": "<credential_id>"
    },
    "name": "discover_managed_clusters"
  }
}

Input Schema

NameRequiredDescriptionDefault
providerYesManaged Kubernetes provider.
credential_idYesUUID of the provider credential (from list_credentials).

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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=true, and the description reinforces this while adding real context: it calls the provider API so it may take a few seconds, and it flags which clusters are already imported. Minor gaps remain (no mention of pagination limits or behavior on an invalid/expired credential), which keeps it off a 5.

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 action and scope, then alternatives, then the latency caveat — a sensible order with no filler sentences. The one inefficiency is re-listing the eight provider strings that are already enumerated in the schema.

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?

There is no output schema, so enumerating returned fields (name, location, version, status, node count, node pools) plus the imported marker is exactly what an agent needs to plan around the result. Latency disclosure and the read-only note round it out for a simple two-parameter 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 both parameters are already documented (provider enum, credential UUID from list_credentials). The description restates the provider list, which duplicates the enum rather than adding meaning, so the 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?

States a specific verb+resource (list managed Kubernetes clusters in the provider account behind a credential) and adds scope detail — marking already-imported ones and the fields returned. It is clearly distinguishable from list_managed_k8s_options (catalogue for NEW clusters) and import_managed_cluster (the follow-up action).

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 an explicit sequencing instruction ('Use this before import_managed_cluster') and an explicit exclusion ('list_managed_k8s_options is the catalogue for creating NEW clusters, not this'). Nothing is left to inference about when to pick this tool.

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.