Skip to main content
Glama

Delete pod

delete_pod
Destructive

Delete a specific pod. If managed by a controller (Deployment, StatefulSet, etc.), a new pod will be created automatically.

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

Input Schema

NameRequiredDescriptionDefault
dry_runNoIf true, preview the change without executing it.
pod_nameYesName of the pod to delete.
namespaceYesKubernetes namespace where the pod is located.
cluster_idYesAnkra cluster id (UUID) the call targets. Discover ids with list_clusters.
grace_period_secondsNoGrace period for pod termination in seconds.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

The destructive annotations already warn that this is a destructive, non-idempotent write. The description adds useful behavioral context by explaining that a controller-managed pod will be recreated automatically, which goes beyond the annotation flags.

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?

The description is two short sentences, front-loads the operation, and immediately adds the most important side effect. There is no redundant or filler wording.

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 destructive delete operation, the annotations cover the safety profile and the schema fully documents parameters including dry_run and grace period. The description contributes the key controller-recreation behavior, though it could say more about alternatives and irreversible effects.

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 are already documented, including dry_run and grace_period_seconds. The description adds no additional parameter meaning beyond what the schema provides, so it sits at the baseline for fully documented parameters.

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 and resource: 'Delete a specific pod.' It is clearer than a generic delete tool, but it does not explicitly differentiate itself from related siblings such as restart_deployment or delete_persistent_volumes.

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?

The description explains what happens when the pod is controller-managed, but gives no explicit when-to-use or when-not-to-use guidance. It does not point agents to alternatives such as restart_deployment or describe when pod deletion is preferable to another operation.

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.