Skip to main content
Glama
happypod-mcp

happypod-mcp

Official
by happy-pod

Roll back pod

rollback_pod
Destructive

Restore an earlier successful deployment live without rebuilding to recover an app broken by a recent deploy.

Instructions

Put an earlier successful deployment back live (no rebuild). The quickest fix when a new deploy broke the app.

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": {
      "podId": "<podId>",
      "deploymentId": "<deploymentId>"
    },
    "name": "rollback_pod"
  }
}

Input Schema

NameRequiredDescriptionDefault
podIdYesPod id
deploymentIdYesDeployment id

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false, idempotentHint=false and openWorldHint=true, so the safety profile is covered. The description adds one genuinely useful behavioral fact, that no rebuild occurs and an existing prior deployment is simply re-activated, but says nothing about whether the currently live deployment is replaced or retained, or about downtime.

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 with zero filler; the primary effect is stated first and the qualifying condition second. Every clause carries information an agent needs.

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 two-parameter mutation tool with rich annotations and no output schema, the description covers what it does, when to reach for it, and the key no-rebuild trait. What remains unsaid, such as the fate of the current live deployment and whether deploymentId must come from this pod's history, is minor but not trivial for a destructive operation.

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 coverage is 100%, so both required parameters are documented in structured data and the baseline is 3. The phrase "earlier successful deployment" does add a constraint beyond the schema's bare "Deployment id" label, implying the id must refer to a previously successful release, but neither parameter is mentioned by name.

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 uses a concrete effect ("put an earlier successful deployment back live") and a parenthetical qualifier ("no rebuild") that separates it from deploy_pod or restart_pod. The verb is paraphrased rather than stated as "roll back", but the resource and effect are unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

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

It gives a clear triggering condition: "the quickest fix when a new deploy broke the app". It does not state when not to use it or name the competing recovery tools (restart_pod, deploy_pod, diagnose_pod) an agent might weigh instead.

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