Skip to main content
Glama

sitekick_release_rollback

DestructiveIdempotent

Roll back exactly the browser-approved release using the returned publication_request. A tool confirmation cannot issue approval.

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": {
      "payload": "<payload>",
      "site_ref": "<site_ref>",
      "idempotency_key": "<idempotency_key>"
    },
    "name": "sitekick_release_rollback"
  }
}

Input Schema

NameRequiredDescriptionDefault
payloadYes
site_refYes
idempotency_keyYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior3/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 safety profile is covered structurally. The description adds genuinely non-annotation context by disclosing the approval gate and that a tool confirmation cannot substitute for approval, but it says nothing about what state is restored, whether the rollback is reversible, or how idempotency replay behaves.

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 with the precondition and the approval warning front-loaded and no filler. The only weakness is that the second sentence ('A tool confirmation cannot issue approval') is a warning stated in isolation, while the undefined 'publication_request' term costs clarity even though it costs no length.

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

Completeness2/5

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

This is a destructive, open-world mutation with a nested payload and zero schema description coverage, which demands more explanation than two sentences supply. An output schema exists so return values need not be described, but the missing detail on parameter meaning and rollback effects leaves the agent under-equipped to invoke it safely.

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

Parameters2/5

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

Schema description coverage is 0% and there are three required parameters including a nested payload, so the description carries the full explanatory burden. It only obliquely gestures at approval_id via 'browser-approved' and never mentions operation_id, site_ref, or the idempotency_key contract, leaving most parameters undocumented in both places.

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 gives a specific verb ('Roll back') tied to a specific resource ('the browser-approved release'), which separates it from sibling operations like sitekick_release_activate or sitekick_release_prepare. It loses a point because 'publication_request' is introduced without definition and does not map onto any named schema parameter, leaving the exact object being rolled back slightly ambiguous.

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?

It implies a precondition: the call must reuse a 'returned publication_request', so the agent knows a prior step is required. It also warns that tool confirmation is not approval, which is real usage guidance, but it never states when to choose rollback over activation or what to do if no approval exists.

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