Skip to main content
Glama

Restart an App's Last Release

varity_redeploy
Destructive

Restart an already deployed app from its last successful release, using the saved commit and configuration while keeping the same URL; it will not include new commits.

Instructions

Restart an app that is ALREADY deployed from its last successful release, at that release's saved commit and configuration. The app keeps the same deployment and URL. It does not pick up new commits: to ship new code, push it and call varity_deploy again with the same app_name. An app with no successful release cannot be restarted. Redeploy restarts dynamic and container apps only; for a static site, push the change and call varity_deploy again with the same app_name. Configure secrets through an approved secret-safe interface. To create a NEW deployment instead, use varity_deploy.

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

Input Schema

NameRequiredDescriptionDefault
nameYesThe subdomain / app name of the existing deployment to redeploy, the slug in https://varity.app/<name>/. Example: 'my-api'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.0.0

TDQS

A4.1/5.0
Behavior3/5

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

Adds real behavior beyond the annotations: the restart reuses the saved commit and configuration, keeps the same deployment and URL, and fails for apps without a successful release. However, the annotations flag destructiveHint=true and idempotentHint=false on what is a live-service restart, and the description never mentions downtime, in-flight traffic interruption, or why the operation is destructive/non-idempotent — the key risk an agent should weigh before calling.

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?

Front-loaded with the core action and its constraint (already deployed, saved commit), then escalates to alternatives. Slightly repetitive: the instruction to push and call varity_deploy with the same app_name appears twice, and the closing 'to create a NEW deployment, use varity_deploy' restates the earlier contrast.

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 one-parameter tool with no output schema, the description covers the decision-relevant facts: what state is used, what is preserved, what fails, and which app types and alternatives apply. The omission is operational expectation — whether the restart causes downtime and what the call returns — which is meaningful given destructiveHint=true.

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 the single 'name' property already documents the slug format, pattern, and an example. The description adds only the indirect point that the same app_name is reused with varity_deploy, so it neither needs to nor does add parameter-level meaning; baseline 3 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?

Specific verb and resource: restart an already-deployed app from its last successful release, at that release's saved commit and configuration. It also states scope boundaries (dynamic and container apps only; static sites excluded) and contrasts itself with varity_deploy, so an agent can distinguish it from its closest sibling without consulting schemas.

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

Usage Guidelines5/5

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

Explicit when-to-use and when-not-to-use: use this to restart existing code, but push and call varity_deploy to ship new commits; an app with no successful release cannot be restarted; static sites must use varity_deploy instead; to create a new deployment, use varity_deploy. It even routes secret configuration to an approved secret-safe interface rather than this tool.

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