Skip to main content
Glama

rollback_sulvo_activation

Destructive

Return the workspace domain to publisher-owned backup-only serving.

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": {
      "workspaceId": "<workspaceId>"
    },
    "name": "rollback_sulvo_activation"
  }
}

Input Schema

NameRequiredDescriptionDefault
inputNoFields required by this journey action.
workspaceIdYesActivation workspace identifier returned by the start or status tool.
outputFormatNomarkdown
idempotencyKeyNoOptional retry key. Reuse it when retrying the same mutation.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / input / propertyNames
      Added value: +{
      +  "type": "string"
      +}
  2. First observed

TDQS

C2.8/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is covered. The description adds the useful outcome detail that the domain ends up in backup-only serving, but it omits whether the rollback is reversible, what happens to existing placement mappings or ad units, and whether it requires confirmation or specific permissions — significant gaps 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?

A single front-loaded sentence with no filler. It is efficiently written, though efficiency here shades into under-specification rather than deliberate brevity, which keeps it from a 5.

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, state-changing operation with a nested free-form `input` object, an idempotency key, and no output schema. One sentence cannot cover preconditions, blast radius (which units/placements are affected), or how to verify success afterwards, so an agent has little basis for calling it safely.

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 75%, with workspaceId and idempotencyKey documented inline, so the schema carries most of the load. The description adds nothing about the nested `input` object or the outputFormat enum, so it neither compensates for the remaining gap nor misleads. Baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a state transition for a specific resource (the workspace domain goes back to publisher-owned backup-only serving), which pairs with the verb 'rollback' in the name. But 'publisher-owned backup-only serving' is internal jargon and the description never says plainly that it undoes a Sulvo activation, nor does it distinguish itself from siblings like submit_sulvo_activation_workspace or get_sulvo_activation_smoke_status.

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, no stated preconditions (e.g. an activation must currently be live), and no reference to any alternative tool. The agent must infer entirely from the name that this is the undo path for an activation.

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