Skip to main content
Glama

Acknowledge Operation Recovery

acknowledge_operation_recovery

Acknowledge a reviewed reconciliation of uncertain Premiere operations after inspecting current host state. Confirms resolution using exact recovery and host-state revisions; consumed operation IDs cannot be replayed or retried.

Instructions

Acknowledge user-reviewed reconciliation of uncertain execution after current-state inspection. Requires the exact latest recovery and host-state revisions. Consumed operation IDs remain unavailable for replay; acknowledgement does not undo or retry a host edit.

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": {
      "backend": "<backend>",
      "expected_recovery_revision": "<expected_recovery_revision>",
      "expected_host_state_revision": "<expected_host_state_revision>",
      "reviewed": "<reviewed>"
    },
    "name": "acknowledge_operation_recovery"
  }
}

Input Schema

NameRequiredDescriptionDefault
backendYesExecution backend whose uncertain operations should be inspected.
reviewedYesTrue only after reviewing current host state and reconciling the uncertain operations.
idempotency_keyNoOptional client-chosen key (1-128 chars of A-Z a-z 0-9 . _ : -) for this intended edit. Pass a fresh key per edit and reuse it only when retrying that same edit, for example after a client-side timeout. A repeat with the same tool, key and arguments is not run again: while the first call is running it fails with IDEMPOTENCY_IN_PROGRESS (poll get_last_operations); after it finished it returns the original outcome marked replayed. A definite failure with nothing applied (receipt outcome not_applied) may be retried with the same key. Reusing a key with different arguments fails with IDEMPOTENCY_KEY_REUSED. Scoped to this MCP session (the stdio server process, or the HTTP server process when Streamable HTTP is stateless per request) and held in memory only (200 keys, 1 hour); it does not survive a restart or reconnect. Read-only invocations are never deduplicated.
expected_cep_targetNoOptional reviewed CEP sequence/clip identity and exact tick ranges. Checked before every generated command; UXP refuses this CEP-only guard.
expected_project_pathNoOptional absolute saved-project path. Every generated CEP command refuses before its body when the active project differs or is unsaved. UXP commands refuse this CEP-only guard; local-only tools do not inspect Premiere. Omit to keep existing behavior.
expected_recovery_revisionYesCEP recoveryRevision or UXP transport.recoveryRevision returned by inspection.
expected_host_state_revisionYesExact hostStateRevision returned by the latest inspected bounded host state.
expected_panel_recovery_revisionNoUXP panel.recoveryRevision returned by inspection; required for UXP.
expected_shared_recovery_revisionNoUXP shared.recoveryRevision when shared Premiere execution recovery is required.

Output Schema

NameRequiredDescriptionDefault
okYesWhether the tool completed successfully.
dataNoTool-specific result data when ok is true; on failure, diagnostic detail when the tool provides it.
toolYesThe registered MCP tool name.
errorNoFailure detail when ok is false.
receiptNoVersioned common mutation receipt; success never implies rendered verification.
idempotencyNoPresent when idempotency_key deduplicated this call: replayed is true when the original outcome was returned instead of running again.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.30.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations only say readOnly=false, destructive=false, idempotent=false; the description adds real behavioral context beyond them — that consumed operation IDs cannot be replayed and that acknowledgement neither undoes nor retries a host edit. It also discloses the optimistic-concurrency requirement for the latest revisions. It does not specify the failure mode on a stale revision, but the non-destructive, non-retrying semantics are clearly conveyed.

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?

Three short sentences, front-loaded with the action and prerequisite, then the side-effect warnings. No filler and nothing repeated. It could be tightened slightly by naming the inspection tool directly rather than describing the inspection generically.

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?

For a mutation-adjacent acknowledgement tool with 100% schema coverage and an output schema, the description covers intent, prerequisite ordering, revision staleness, and the no-retry/no-undo consequences. The main gap is the unspecified error behavior when revisions are stale and the absence of a named inspection sibling.

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 100% and the nine parameters (including the nested CEP target and the elaborately documented idempotency_key) are fully annotated in the schema. The description adds only the qualifier 'exact latest' for the two revision parameters, which the schema already frames as 'returned by inspection'. Baseline 3 is appropriate when the schema does nearly all the work.

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 — acknowledging a user-reviewed reconciliation of uncertain execution — which is materially more informative than the title 'Acknowledge Operation Recovery'. The phrase 'after current-state inspection' implicitly distinguishes it from inspect_operation_recovery, though it does not name that sibling. The domain jargon ('uncertain execution', 'reconciliation') makes the operation understandable to an informed agent but not instantly obvious.

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?

Usage is only implied: 'after current-state inspection' suggests the prerequisite of running inspection first, and 'does not undo or retry' rules out a retry intent. It never names inspect_operation_recovery or undo as the alternatives, nor states what to do when revisions are stale. An agent can infer the workflow but must guess at the routing.

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

Deploy Server

Other Tools