Skip to main content
Glama
Sign In
k8scortex-mcp

k8scortex-mcp

by apatilgtn
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

restart_pod

Delete a pod to force a restart for deployments or replicasets.

Instructions

Deletes a pod to force a restart. Usually managed by a deployment/replicaset.

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>",
      "podName": "<podName>"
    },
    "name": "restart_pod"
  }
}

Input Schema

NameRequiredDescriptionDefault
dryRunNoIf true, simulates the action without making changes
clusterNoTarget cluster name (default: 'default')
podNameYesThe name of the pod to restart
namespaceYesThe Kubernetes namespace

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.2

TDQS

A3.6/5.0
Behavior3/5

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

The description discloses the destructive action (deleting a pod) and the restart effect. However, it lacks details on required permissions, service impact, or recovery behavior, which is noteworthy given no annotations are provided.

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 sentences are front-loaded with the action and key context. No extraneous words.

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?

With no annotations and no output schema, the description is too minimal. It does not explain critical aspects like the dryRun parameter's purpose, cluster selection, or the typical outcome (pod recreation by controller). This is a gap for a tool with 4 parameters.

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?

All four parameters are documented in the schema (100% coverage), so the description adds no additional meaning beyond what's already there. Baseline score 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 clearly states the tool deletes a pod to force a restart, which is a specific verb-resource action. It distinguishes from sibling tools like list_pods and get_pod_logs.

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?

The hint 'Usually managed by a deployment/replicaset' provides some context about typical usage, but it doesn't explicitly state when to use this tool versus alternatives like scale_deployment or rollout_undo.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools