Skip to main content
Glama

Activate a release

activate_release
DestructiveIdempotent

Switches an authorized project’s active route to a completely published retained release with revision checks. Returns the previous release as the rollback target.

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

Input Schema

NameRequiredDescriptionDefault
project_idYesExact stable project ID. Resolve it first. Never invent an update target.
release_idYes
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

A3.6/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, idempotentHint=true and openWorldHint=true, so the description adds real value by disclosing the revision-check behavior and that the previous release is returned as a rollback target — the latter matters especially since no output schema exists. It does not explain the overwrite/overwrite_confirmation path that the schema implies, so the destructive nuance is only partly covered.

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 tight sentences with the core action front-loaded and the return value second; nothing is padded. 'With revision checks' is the only slightly vague phrase, but it is short enough not to waste space.

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 six-parameter destructive mutation the description covers the action, preconditions and rollback return, which is a reasonable core. It omits what state changes for the currently active route and how the overwrite-confirmation flow is meant to be sequenced, leaving meaningful gaps for a destructive write with no output schema.

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 83% schema description coverage, the schema already carries parameter meaning, including the overwrite-consent and revision fields. The description's phrase 'with revision checks' gestures at expected_revision/overwrite_revision but adds no format or sequencing detail beyond the schema, so the baseline 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?

The description names a specific verb and resource: it 'switches an authorized project's active route' to a published retained release. That is concrete enough to distinguish it from deployment-creation or listing tools, but it never names the closest sibling (rollback_project) or states how activation differs from it.

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?

Preconditions are implied ('authorized project', 'completely published retained release'), which tells the agent roughly when the call can succeed, but there is no explicit when-to-use versus rollback_project or begin_deployment, and no stated exclusion or failure path.

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