Skip to main content
Glama

Scale StatefulSet

scale_statefulset
Destructive

Scale a StatefulSet to a specified number of replicas.

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": {
      "namespace": "<namespace>",
      "statefulset_name": "<statefulset_name>",
      "replicas": "<replicas>",
      "cluster_id": "<cluster_id>"
    },
    "name": "scale_statefulset"
  }
}

Input Schema

NameRequiredDescriptionDefault
dry_runNoIf true, preview the change without executing it.
replicasYesTarget number of replicas (0-100).
namespaceYesKubernetes namespace where the StatefulSet is located.
cluster_idYesAnkra cluster id (UUID) the call targets. Discover ids with list_clusters.
statefulset_nameYesName of the StatefulSet to scale.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.8/5.0
Behavior2/5

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

Annotations already flag this as destructive, non-readOnly and non-idempotent, so the safety profile is known. The description adds nothing beyond that: it does not warn that scaling down terminates pods in descending ordinal order, does not mention volume/PVC retention implications, and does not surface the dry_run preview option that the schema exposes.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single efficient sentence with no filler and the core action front-loaded. However, the terseness crosses into under-specification for a destructive operation, so the brevity does not fully earn its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a destructive mutation with no output schema, the description should at minimum note the dry_run preview path and the effect of scaling to zero or down. Neither is present, leaving the agent reliant entirely on the schema and annotations to call it safely.

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%, with every parameter including dry_run, namespace, cluster_id and the 0-100 replica range fully documented in the schema. The description only echoes the replicas concept and adds no interpretation beyond the schema, which is the expected baseline when the schema does the heavy lifting.

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?

The description states a specific verb (Scale) and resource (StatefulSet) plus the target value, so an agent immediately knows the operation. It does not distinguish itself from the sibling scale_deployment, leaving the agent to infer that the difference is purely the workload type.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use or when-not-to-use guidance, no mention of the sibling scale_deployment as an alternative, and no stated preconditions such as the StatefulSet already existing or the cluster being reachable. The agent must infer all routing decisions from the name alone.

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.