Skip to main content
Glama

Get cluster platform settings

get_cluster_platform_settings
Read-only

Read one of a cluster's platform settings. report picks it: labels (the cluster's labels, which place it in dynamic groups, and the keys Ankra reserves),control_plane_self_heal and worker_self_heal (whether Ankra restarts a NotReady node of that kind, and the last incident it handled; the twins of ankra cluster control-plane-heal get and worker-heal get), held_platform_updates (the platform component updates Ankra held back for this cluster), stack_variables (one stack's variables as stored; needs stack_name; the twin of ankra cluster stacks variables list), k3s_disabled_components (the k3s components a self-managed provider cluster runs without) and load_balancer_plan (an UpCloud cluster's ingress load balancer plan and the plans its live load balancers run on). held_platform_updates, k3s_disabled_components and load_balancer_plan need clusters.read. Read-only: it changes no label, switch, update, variable or plan.

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": {
      "report": "<report>"
    },
    "name": "get_cluster_platform_settings"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoheld_platform_updates: the page to read (default 1); total_pages says how many there are.
reportYesWhich setting to read.
page_sizeNoheld_platform_updates: cards to return, 1 to 100 (default 25).
cluster_idNoCluster id (UUID). Optional when the conversation is bound to a cluster.
stack_nameNostack_variables: the stack whose variables to read.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior3/5

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

Annotations already establish readOnlyHint=true, and the description reinforces that it changes nothing. It adds useful authorization context ('need clusters.read') and explains the meaning of each report's contents, but it does not cover failure behavior, rate limits, or output shape.

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?

The purpose is front-loaded and the dense enumeration is largely earned by seven distinct report values. However, it is delivered as one long run-on inventory and the final read-only sentence partly restates the annotation.

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?

For a seven-variant read tool with no output schema, the description is unusually complete: it explains what each report returns, prerequisites, permissions, and that the operation is read-only. Nothing essential to selecting and invoking it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline would be 3, but the description goes well beyond the schema by defining each report enum value, its returned content, and dependencies like stack_name for stack_variables. This directly improves parameter selection.

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 description gives a specific verb and resource ('Read one of a cluster's platform settings') and then enumerates every report value with what each represents. An agent can distinguish this from general cluster-detail siblings without opening the schema.

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?

It clearly explains how to choose among the report values and notes dependencies such as stack_name for stack_variables and clusters.read for three reports. It stops short of explicitly naming when to use another sibling tool instead, so it is clear context without full alternative routing.

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.