Skip to main content
Glama

rehearsal_manage

Run and monitor zero-risk migration rehearsals on disposable database copies; start, check status, cancel, summarize runs, and clean up copies to reclaim disk space.

Instructions

Execute and monitor zero-risk migration rehearsals on disposable copies.

Actions:

  • 'start': Rehearse a pipeline on a disposable copy (confirm=false returns plan & disk estimate).

  • 'status': Poll progress of running or completed rehearsal and view risk report.

  • 'cancel': Abort a running rehearsal while preserving the copy for inspection.

  • 'last_run': Summarize latest pipeline run: step progress and frequent Odoo errors.

  • 'drop_copies': Drop expired or named disposable rehearsal copies to reclaim disk space.

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": {
      "action": "<action>"
    },
    "name": "rehearsal_manage"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionYes
methodNoClone methodauto
sourceNoSource database to clone from
confirmNofalse = preview/plan only; true = execute
copy_idsNoSpecific copy IDs to drop
pipelineNoPipeline name from policy
plan_hashNoFingerprint from confirm=false preview
expired_onlyNoDrop only expired copies (default false)
rehearsal_idNoRehearsal identifier

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.3

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare openWorld=false and destructiveHint=false, and the description reinforces this with 'zero-risk' and 'disposable copies', plus useful extra behavior: confirm=false returns a plan and disk estimate, cancel preserves the copy, and dropping is limited to expired or named copies. It does not cover permissions, whether 'start' blocks or is async, or rate/disk limits, so it stops short of a 5.

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?

A single front-loaded summary sentence followed by one tight bullet per action; no filler or repetition, and the highest-signal constraint (disposable copy, zero risk) appears first.

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

Completeness4/5

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

With 9 parameters, an output schema, and annotations already present, the description covers the action space well, but it never maps which parameters belong to which action (e.g., that plan_hash pairs with confirm=true on 'start'), leaving the agent to infer that from the schema alone.

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 coverage is 89%, so the schema already documents most parameters. The description clarifies the intent of 'confirm' (plan vs execute) and implicitly ties 'expired_only'/'copy_ids' to drop_copies and 'rehearsal_id' to status, but says nothing about method, source, pipeline, or plan_hash, so it adds only marginal meaning.

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

Purpose5/5

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

States a specific verb and resource ('Execute and monitor migration rehearsals on disposable copies') and then enumerates all five actions with concrete outcomes, so an agent can tell exactly what each mode does without opening the schema.

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?

Each action is given an explicit usage context — 'start' for rehearsing with a preview path, 'status' for polling, 'cancel' to abort while keeping the copy, 'drop_copies' to reclaim disk. It lacks explicit when-not-to-use guidance or named alternatives among siblings such as migration_audit or db_inspect, which keeps it below a 5.

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