Skip to main content
Glama

recovery_activate

DestructiveIdempotent

Resume a restored service after confirming the original controller is stopped, keeping original job identities.

Instructions

Resume a restored service after confirming the original controller is stopped. Keep original job identities.

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": {
      "previous_controller_stopped": "<previous_controller_stopped>",
      "op_id": "<op_id>"
    },
    "name": "recovery_activate"
  }
}

Input Schema

NameRequiredDescriptionDefault
op_idYes
previous_controller_stoppedYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/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 readOnlyHint=false, so the safety profile is covered structurally; the description adds genuinely new context by stating that original job identities are preserved. It never says what is destroyed or invalidated when activation proceeds, which is the key unknown for a destructive operation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences with the precondition and the identity-preservation guarantee front-loaded; nothing is redundant or padded.

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?

An output schema exists, so return values need no explanation. However, for a destructive, idempotent activation step with two required parameters and zero schema descriptions, the definition leaves the op_id operand and the consequences of activation unaddressed.

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%, so the description must carry parameter meaning. It conveys the intent of previous_controller_stopped ('after confirming the original controller is stopped'), but op_id is never mentioned in either the schema or the description, leaving one of two required parameters unexplained.

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?

States a specific verb and object ('Resume a restored service') plus the gating condition, which is far more informative than the name alone. It does not name or contrast any sibling recovery/control tool, so an agent must still infer that this is the activation step in a restore workflow.

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?

The clause 'after confirming the original controller is stopped' gives an explicit precondition for when to call this. It stops short of any when-not guidance or named alternative for the case where the controller is still running, so the agent must improvise that branch.

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