Skip to main content
Glama

thanaton_rollback

Perform atomic rollback of production traffic to a previous deployment snapshot to recover from failed deployments.

Instructions

Instant atomic rollback of production traffic to a previous deployment snapshot in 8.2ms.

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": {
      "project_id": "<project_id>",
      "deployment_id": "<deployment_id>"
    },
    "name": "thanaton_rollback"
  }
}

Input Schema

NameRequiredDescriptionDefault
project_idYesTarget project ID
deployment_idYesTarget snapshot deployment ID to restore

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.6

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations provided, the description carries the full burden and only discloses atomicity and a latency figure ('atomic', '8.2ms'). It says nothing about whether the rollback is itself reversible, what happens to the currently active deployment, whether in-flight requests are dropped, required permissions, or failure behavior — all critical for an operation that mutates production traffic.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

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

A single front-loaded sentence with no padding, and the destructive action is stated first. The trailing '8.2ms' is unverifiable marketing-style precision that adds little decision value, a minor blemish.

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?

For a production-mutating tool with zero annotations and no output schema, the description should explain what the caller observes on success and what is left behind or destroyed. It instead stops after a speed claim, so an agent cannot predict the operation's side effects or result.

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% and both parameters are documented there; the description's 'previous deployment snapshot' merely restates the schema's 'snapshot deployment ID to restore'. Baseline 3 is appropriate since the schema does all the parameter work.

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 names a specific verb (rollback) and a specific resource (production traffic, to a previous deployment snapshot), which is far more informative than the bare tool name. It does not explicitly name a sibling or contrast itself with thanaton_promote, so an agent must infer the promote/rollback division of labor.

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?

There is no explicit guidance on when to call this rather than thanaton_promote or thanaton_deploy_code, no prerequisites, and no stated conditions of use. The phrase 'rollback of production traffic' only implies the situation loosely, leaving the agent to guess at the trigger condition.

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