Skip to main content
Glama
delimit-ai

delimit

Official
by delimit-ai
OverviewSchemaRelated ServersScoreDiscussions
Python
Hybrid

Delimit Deploy Rollback

delimit_deploy_rollback
Destructive

Roll back an environment to a previous SHA to fix regressions detected after verification. Reverses the live deployment to a known-good revision (Delimit Pro required).

Instructions

Roll back an environment to a previous SHA (Pro).

When to use: when delimit_deploy_verify shows a regression and you need to revert the running deployment to a known-good revision. When NOT to use: to deploy a new version forward (delimit_deploy_plan -> _build -> _publish) — rollback is reversal-only.

Sibling contrast: delimit_deploy_publish moves an env forward; this moves it back to a prior to_sha.

Side effects: gated by require_premium. Calls backends.deploy_bridge.rollback which mutates the running environment to point at to_sha.

Prerequisite: requires Delimit Pro. An unlicensed call returns {"error": ..., "upgrade": "https://delimit.ai/pricing"} without running.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
appNoApplication name.
envNoTarget environment.
to_shaNoTarget SHA to roll back to. If None, the backend selects the previous deployed SHA.
repo_pathNoExplicit Git worktree root.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed1 schema field changedv4.13.2
    • addedInput schema / properties / repo_path
      Added value: +{
+  "default": "",
+  "description": "Explicit Git worktree root.",
+  "type": "string"
+}
  2. Changed3 schema fields changedv4.7.9
    • addedInput schema / properties / app / description
      Added value: +"Application name."
    • addedInput schema / properties / env / description
      Added value: +"Target environment."
    • addedInput schema / properties / to_sha / description
      Added value: +"Target SHA to roll back to. If None, the backend selects the previous deployed SHA."
  3. Changed3 schema fields changedv4.5.5
    • addedInput schema / properties / app / default
      Added value: +""
    • addedInput schema / properties / env / default
      Added value: +""
    • removedInput schema / required
      Removed value: -[
-  "app",
-  "env"
-]
  4. First observedv0.1.0

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already flag destructiveHint=true, but the description adds substantial behavioral detail: the call is gated by require_premium, invokes backends.deploy_bridge.rollback, mutates the running environment, and returns a specific error payload with an upgrade URL when unlicensed. This goes well beyond the annotation hints and clearly sets expectations for side effects and failure behavior.

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 well structured with clear labeled sections: purpose, when to use, when not to use, sibling contrast, side effects, and prerequisite. Every sentence adds necessary information, and the most important scoping details are front-loaded.

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

Completeness5/5

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

Given the tool's complexity and the presence of both input and output schemas, the description covers all essential operational guidance: trigger condition, exclusion criteria, reversal-only behavior, side effects, licensing prerequisite, and failure mode. No critical information needed to invoke it correctly is missing.

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 each parameter already has its own description. The tool description adds only minimal extra insight by referencing 'prior to_sha,' while the schema already explains that null selects the previous deployed SHA. The schema carries the semantic weight, so baseline 3 is appropriate.

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?

The description opens with a clear verb and resource: 'Roll back an environment to a previous SHA.' It also distinguishes the tool from delimit_deploy_publish by stating that publish moves forward while this moves backward, so an agent can identify the correct tool without ambiguity.

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' sections define the exact scenario (delimit_deploy_verify shows a regression) and explicitly rule out forward deploys. It also names the sibling tool and the condition that selects it, leaving no inference required.

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/delimit-ai/delimit-mcp-server'

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