Skip to main content
Glama

Roll back a project

rollback_project
DestructiveIdempotent

Restores a retained earlier release by changing the project’s active route pointer with revision checks. No rebuild or file copying occurs.

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

Input Schema

NameRequiredDescriptionDefault
project_idYesExact stable project ID. Resolve it first. Never invent an update target.
release_idNo
idempotency_keyYesUnique write key. Reuse the same key and input after an uncertain response.
expected_revisionNoOriginal base_revision in local .deploymonster.json; never substitute current server revision before reconciliation.
overwrite_revisionNoExact remote revision the USER explicitly agreed to overwrite after seeing change summary.
overwrite_confirmationNoOnly after explicit user overwrite choice; never auto-confirm.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

The annotations already declare destructive=true, idempotent=true, and readOnly=false, so the safety profile is known. The description adds real value beyond that by disclosing that only a route pointer is changed and that no rebuild or file copying occurs, which tells an agent the blast radius is configuration-only. However it omits the overwrite-confirmation flow and the fact that the change is not a content redeploy, and it doesn't say whether the rollback is itself reversible.

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?

Two short sentences, front-loaded with the mechanism and followed by the important negative constraint. Nothing is padding, though the 'with revision checks' clause is slightly cryptic and could have been made explicit without adding length.

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 destructive, six-parameter mutation with no output schema, the description explains the mechanism but omits the overwrite-confirmation path and the irreversibility/recoverability story, which matter most for an agent deciding whether to proceed. It is adequate because the rich schema descriptions cover parameter mechanics, but the destructive-action context is thinner than the tool warrants.

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 83%, so the schema already documents project_id, idempotency_key, expected_revision, and overwrite_confirmation in detail. The description adds only the vague phrase 'with revision checks', which gestures at expected_revision without explaining reconciliation or the overwrite path. Baseline 3 is appropriate when the schema carries this much of the load.

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?

Uses a specific verb and resource: restores a retained earlier release by repointing the project's active route. That is concrete enough for an agent to know exactly what happens, but it never names how it differs from siblings such as activate_release or begin_deployment, so the boundary work is left to inference.

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 when-to-use guidance and no mention of alternatives or preconditions: nothing says when a rollback is preferable to activating a release, or what must be true first (e.g., a retained release existing). The phrase 'with revision checks' hints at a prerequisite but does not state one.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources