Skip to main content
Glama
Sign In
@vertracloud/mcp

@vertracloud/mcp

Official
by vertracloud
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

rollback_app

Destructive

Revert an application to a previous release and restart it while preserving stored data; optionally restore environment variables saved with that release.

Instructions

Rolls the application back to a previous release: its code goes back to that version and the application restarts. Data the application wrote while running is kept. Environment variables are kept as they are unless restore_environment is true, which also needs the apps:envs scope; run preview_rollback first in that case. Possible errors: RELEASE_EXPIRED, RELEASE_ALREADY_ACTIVE, RESTORE_COOLDOWN, OPERATION_IN_PROGRESS. (scope: apps:write)

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": {
      "id": "<id>",
      "release_id": "<release_id>"
    },
    "name": "rollback_app"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesApplication ID
release_idYesRelease ID (from `list_releases`)
workspace_idNoID of the workspace that owns the resource, if any
restore_environmentNoAlso restore the environment variables saved with that release (default: false)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.3.0
    • addedInput schema / properties / id / minLength
      Added value: +1
    • addedInput schema / properties / release_id / minLength
      Added value: +1
  2. Addedv0.2.1

TDQS

A4.6/5.0
Behavior5/5

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

The description adds substantial behavior beyond the annotations: code reverts, the application restarts, application-written data is kept, and environment variables are preserved unless explicitly restored. It also discloses the additional `apps:envs` scope and lists concrete error conditions, which is unusually complete for a destructive mutation.

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?

The description is front-loaded with the core action and effects, then moves to conditional behavior, errors, and scope. It is dense but efficient; every sentence contributes useful operational context, though the error list makes it slightly heavy.

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?

For a destructive mutation with no output schema, the definition covers effects, preserved state, restart behavior, conditional permissions, preflight guidance, and failure modes. Together with annotations, it provides enough context for an agent to call the tool correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is already 100%, so the baseline would be 3. The description still adds meaningful semantics for `restore_environment`, including that it restores saved environment variables, requires an extra scope, and should be preceded by `preview_rollback`.

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 states a specific verb and resource: it rolls the application back to a previous release, with concrete effects on code and restart behavior. It also explicitly distinguishes the action from `preview_rollback`, so an agent can identify the tool without consulting siblings.

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 conditional prerequisite: run `preview_rollback` first when `restore_environment` is true. It does not broadly explain when to prefer rollback over redeploying or other recovery actions, but the main alternative is named with a specific 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