Skip to main content
Glama

Restart deployment

restart_deployment
Destructive

Perform a rolling restart of a deployment by updating its pod template annotation. This causes all pods to be recreated.

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>",
      "cluster_id": "<cluster_id>"
    },
    "name": "restart_deployment"
  }
}

Input Schema

NameRequiredDescriptionDefault
dry_runNoIf true, preview the change without executing it.
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 restart.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/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, so the safety profile is known. The description adds real value beyond that by explaining *how* the destruction happens (pod template annotation update) and its scope (all pods recreated), which tells an agent this is a full rollout rather than a partial change. It stops short of saying whether the restart is availability-preserving, how long it takes, or that the change is reversible by reverting the annotation, which keeps it below 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.

Conciseness5/5

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

Two short sentences, zero filler, and the mechanism plus consequence are front-loaded. Nothing redundant with the title or annotations beyond what is necessary to explain the effect.

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 four-parameter destructive mutation with no output schema, the description covers what the operation does and what changes as a result, which is the essential information. Minor gaps remain around return values, timing, and whether the call blocks until pods are ready, but these are secondary given complete schema coverage and clear annotations.

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%, with every parameter including dry_run documented inline, so the schema carries the parameter burden. The description adds no parameter-level meaning such as how dry_run output differs or which cluster_id source to prefer, so the baseline of 3 applies.

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 states a specific verb and resource ('rolling restart of a deployment') and goes further to name the mechanism ('updating its pod template annotation') and the consequence ('all pods to be recreated'). That level of detail makes it clearly distinguishable from siblings like scale_deployment or park_application_deployment without needing to open 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 Guidelines3/5

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

Usage is only implied: an agent can infer this is the tool for cycling pods, but there is no explicit when-to-use, when-not-to-use, or pointer to an alternative such as scale_deployment or park_application_deployment. No prerequisites (permissions, cluster state, expected downtime) are stated.

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.