Skip to main content
Glama

Plan Shot Match

plan_shot_match

Compare two local video frame samples to measure waveform, parade, and saturation differences and get coarse correction directions for planning a shot match; read-only, no Premiere grading.

Instructions

Compare two bounded local-media frame samples and return measured waveform/parade/saturation deltas plus coarse correction directions. Read-only planning only; it does not grade Premiere or claim that primaries alone can match the shots.

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": {
      "reference_media_path": "<reference_media_path>",
      "target_media_path": "<target_media_path>"
    },
    "name": "plan_shot_match"
  }
}

Input Schema

NameRequiredDescriptionDefault
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.
target_media_pathYesExisting local target video file
expected_cep_targetNoOptional reviewed CEP sequence/clip identity and exact tick ranges. Checked before every generated command; UXP refuses this CEP-only guard.
target_time_secondsNoTarget source time from 0 through 86400 seconds (default: 0)
reference_media_pathYesExisting local reference video file
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.
reference_time_secondsNoReference source time from 0 through 86400 seconds (default: 0)

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

B3.2/5.0
Behavior1/5

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

The description asserts 'Read-only planning only', while the annotations declare readOnlyHint=false — a direct conflict on the very trait the sentence is claiming. An agent reading the prose would conclude nothing is modified, but the structured hint says the tool is not read-only, and the schema's idempotency_key and expected_cep_target guard fields reinforce the mutation framing. The remaining behavioral content (bounded samples, coarse directions, no Premiere grading) is useful but does not resolve this inconsistency.

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 with zero filler: the first front-loads what is compared and what is returned, the second front-loads the scope limitation. Nothing is repeated from the name or the schema.

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 7-parameter tool with nested guard objects and an output schema, the description covers the essentials — input nature, returned measurements, and what the tool refuses to conclude. It omits the idempotency and CEP-guard behavior, but those are documented in the schema and the output schema covers the return shape.

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%, so the schema already carries parameter meaning, and the description adds only the notion of 'bounded local-media frame samples' without explaining the time-offset parameters or the identity guards. Baseline 3 applies when the schema does the heavy lifting.

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?

Names a specific verb and resource — compare two bounded local-media frame samples — and states exactly what comes back (waveform/parade/saturation deltas plus coarse correction directions). The 'Read-only planning only' clause implicitly separates it from the apply_* siblings, though it never names the nearest alternative (match_frame), so differentiation is inferential rather than explicit.

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?

The description sets a clear boundary by stating what the tool is not: it does not grade Premiere and does not claim primaries alone can match the shots. That gives usable scope context, but there is no explicit 'use this instead of match_frame when...' routing, so the agent must infer the planning-vs-applying split from the sibling names alone.

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