Skip to main content
Glama

rollout-history

View deployment rollout history to track changes, identify issues, and manage Kubernetes deployments effectively.

Instructions

Show the rollout history of a deployment

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
deploymentYesThe name of the deployment to check history for
namespaceNoThe namespace of the deployment (optional, defaults to current context namespace)

Implementation Reference

  • Handler function for the 'rollout-history' tool. Executes 'kubectl rollout history deployment/{deployment}' with optional namespace and returns the stdout as text content.
    case "rollout-history": {
      const { deployment, namespace } = args;
      const nsArg = namespace ? `-n ${namespace}` : "";
      const cmd = `kubectl rollout history deployment/${deployment} ${nsArg}`;
      const { stdout } = await execAsync(cmd);
      return {
        content: [{ type: "text", text: stdout || "No rollout history found" }]
      };
    }
  • Input schema and tool registration definition for 'rollout-history' in the tools list returned by ListToolsRequestHandler.
      name: "rollout-history",
      description: "Show the rollout history of a deployment",
      inputSchema: {
        type: "object",
        properties: {
          deployment: { 
            type: "string",
            description: "The name of the deployment to check history for"
          },
          namespace: { 
            type: "string",
            description: "The namespace of the deployment (optional, defaults to current context namespace)"
          }
        },
        required: ["deployment"]
      }
    },
  • server.js:1392-1394 (registration)
    Registration of the ListToolsRequestHandler which returns the tools array containing the 'rollout-history' tool definition.
    server.setRequestHandler(ListToolsRequestSchema, async () => {
      return { tools };
    });
Behavior2/5

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

No annotations are provided, so the description carries full burden for behavioral disclosure. While 'Show' implies a read-only operation, the description doesn't specify what format the history takes, whether it includes timestamps, status changes, or other details. It also doesn't mention any authentication requirements, rate limits, or potential side effects.

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 a single, focused sentence that directly states the tool's purpose without any unnecessary words. It's perfectly front-loaded and wastes no space on redundant information.

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

Completeness3/5

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

For a read-only tool with 2 parameters and no output schema, the description is minimally adequate. However, without annotations or output schema, it should ideally provide more context about what the rollout history includes (e.g., revision numbers, timestamps, status changes) and how it differs from related deployment tools.

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?

With 100% schema description coverage, both parameters are already documented in the schema. The description doesn't add any additional meaning about the parameters beyond what's in the schema descriptions. The baseline score of 3 reflects adequate but minimal value addition.

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 clearly states the action ('Show') and target ('rollout history of a deployment'), making the purpose immediately understandable. However, it doesn't differentiate this tool from potential siblings like 'rollout-status' or 'describe-deployment', which might also provide deployment-related information.

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 provides no guidance on when to use this tool versus alternatives. With siblings like 'rollout-status', 'describe-deployment', and 'list-deployments' available, there's no indication of what makes 'rollout-history' distinct or when it should be preferred over these other deployment-related tools.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/thekaranpargaie/kube-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server