Skip to main content
Glama

thanaton_promote

Promote a staging preview deployment snapshot to 100% production traffic for a project, turning a validated preview into a full production release.

Instructions

Promote staging preview deployment snapshot to 100% production traffic in 6.4ms.

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

Input Schema

NameRequiredDescriptionDefault
project_idYesTarget project ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.6

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full disclosure burden. It does communicate the blast radius (100% of production traffic), which is genuinely useful for a high-impact operation, but says nothing about irreversibility, what happens to the previous production version, required permissions, or whether the operation can be undone.

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?

One front-loaded sentence with the action and effect stated immediately. The trailing 'in 6.4ms' is unverifiable marketing flair rather than operational information, which is the only wasted wording.

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 single-parameter mutation with no output schema and no annotations, the definition should address post-promotion state and reversibility. It covers the traffic cutover but leaves an agent unable to predict what happens to the displaced production deployment or how to recover.

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 a single parameter and 100% schema description coverage, the schema already documents project_id as the target project. The description adds no extra meaning about the parameter, so the baseline of 3 applies.

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?

Specific verb ('Promote') plus resource ('staging preview deployment snapshot') plus target ('100% production traffic'), which an agent can distinguish from generic deploy or spawn siblings. It stops short of naming the sibling that handles the inverse operation (thanaton_rollback), so differentiation is only partial.

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?

Usage is implied rather than stated: promoting a preview to full production traffic is the obvious trigger, and no when-not conditions, prerequisites, or alternatives such as thanaton_rollback or thanaton_deploy_code are mentioned. An agent must infer the decision context from the wording alone.

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