Skip to main content
Glama

Scale deployment

scale_deployment
Destructive

Scale a deployment 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>",
      "deployment_name": "<deployment_name>",
      "replicas": "<replicas>",
      "cluster_id": "<cluster_id>"
    },
    "name": "scale_deployment"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare destructiveHint=true, idempotentHint=false, and readOnlyHint=false, so the safety profile is known without the description. The description adds nothing beyond that: no warning about workload downtime, no note that replicas=0 effectively stops the workload, no mention of the dry_run preview path, and no disclosure of what is returned.

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?

A single front-loaded sentence with no filler or tangential wording. It is efficient, though its brevity reflects under-specification rather than high information density.

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 on 5 parameters with no output schema, the description omits the risky behaviors an agent needs: downtime implications, the replicas=0 case, and the dry_run preview. The schema covers parameter mechanics but the description leaves the operational consequences unstated.

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 all five parameters, including the dry_run flag and the 0-100 replica bounds, are already documented in the schema. The description only echoes the replicas parameter and adds no meaning beyond structured data, making the baseline 3 correct.

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?

States a specific verb and resource ('Scale a deployment') plus the target quantity ('specified number of replicas'), which is enough to distinguish it from unrelated siblings. It does not distinguish it from scale_statefulset or other workload-scaling siblings, so it falls short of a 5.

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 guidance on when to use this versus alternatives such as scale_statefulset, no prerequisites (e.g., cluster access, deployment must exist), and no mention of when to prefer a dry run. The reader gets no routing or precondition information at all.

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.