Skip to main content
Glama

Review Sync Evidence

review_sync_evidence
Read-onlyIdempotent

Validates caller-supplied camera and recorder offset estimates for method agreement and confidence, blocking conflicts and requiring explicit approval of every proposed match.

Instructions

Review caller-supplied camera/recorder offset estimates for independent-method agreement, confidence and conflicting alternatives. All matches require selection; conflicting matches cannot be approved. Does not analyze audio, calibrate confidence or synchronize Premiere.

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": {
      "matches": "<matches>"
    },
    "name": "review_sync_evidence"
  }
}

Input Schema

NameRequiredDescriptionDefault
matchesYesCamera-recorder proposals from already captured local analysis.
rejected_idsNoExplicitly rejected entry IDs. Unselected entries remain pending.
selected_idsNoExplicitly approved entry IDs. Omit for an initial review; an empty array approves nothing.
minimum_confidenceNoRequired confidence on every estimate to label strong agreement; all matches still need approval.
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_review_revisionNoRevision from the initial review; required when selecting or rejecting entries. A changed input requires a new review.
agreement_tolerance_secondsNoMaximum spread between methods for agreement; defaults to 0.04 seconds.

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

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description adds behavioral substance beyond that: every match must be explicitly resolved, conflicts block approval, and confidence values are caller-supplied rather than tool-calibrated. It does not describe the shape of the review result, but the output schema carries that.

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 tight sentences: the action and its criteria come first, the required selection rule second, and the negative scope last. No filler and nothing that merely restates the title.

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 a full output schema, dense annotations and 100% parameter coverage, the description only needs to frame purpose and rules, and it does. A slight gap is that it never frames the two-step flow (initial review producing expected_review_revision, then a follow-up call to select/reject), which lives only in schema field text.

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%, including rich per-field descriptions for estimates, confidence, agreement_tolerance_seconds and the revision guard, so the schema does the heavy lifting. The description reinforces that confidence is caller-supplied and uncalibrated, but adds no syntax or semantics beyond the schema. Baseline 3 is correct.

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?

The description states a specific verb and resource ('Review caller-supplied camera/recorder offset estimates') and enumerates the review criteria: independent-method agreement, confidence, and conflicting alternatives. It also draws a hard negative boundary ('Does not analyze audio, calibrate confidence or synchronize Premiere'), which separates it from sync/analysis siblings without needing a schema read.

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?

It establishes the operating context clearly: input comes from 'already captured local analysis' and the tool only evaluates it. The exclusions in the last sentence tell the agent when not to use this tool, and 'All matches require selection; conflicting matches cannot be approved' conveys the workflow rule. It stops short of naming specific alternatives it hands off to (e.g. the planning/sync tools), so not a 5.

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