Skip to main content
Glama

Inspect Rendered Video Scopes

inspect_rendered_video_scopes
Read-onlyIdempotent

Samples a caller-owned exported video with decoded RGB scopes to declare range, transfer, and primaries evidence, refusing HDR legal-range claims from an 8-bit proxy.

Instructions

Sample a caller-owned exported video using existing decoded RGB scopes and declare range/transfer/primaries evidence. Refuses HDR legal-range claims from an 8-bit RGB proxy; does not prove Premiere render lineage.

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": {
      "output_path": "<output_path>"
    },
    "name": "inspect_rendered_video_scopes"
  }
}

Input Schema

NameRequiredDescriptionDefault
color_rangeNoCaller-declared encoded range; validated metadata is separate.
output_pathYesExisting rendered video to sample.
time_secondsNoOutput-relative sample time, default zero.
color_transferNoCaller-declared transfer function (PQ/HLG remain unsupported for legal-range conclusions).
color_primariesNoCaller-declared primaries.
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.

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 establish that this is a read-only, non-destructive, idempotent inspection. The description adds meaningful behavioral context beyond annotations by stating that it relies on existing decoded RGB scopes, refuses HDR legal-range conclusions from an 8-bit RGB proxy, and does not establish Premiere render lineage. It does not explain return details, but an output schema exists.

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?

The description is two tight sentences with no wasted wording. The core operation is front-loaded, followed by the key limitations.

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 an eight-parameter read-only inspection tool with nested guard objects and an output schema, the description conveys the core evidence and explicitly limits overclaiming. The structured schema covers the optional CEP and project-path guard parameters, so the description is complete enough to invoke correctly, though it could briefly clarify local-only scope.

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 input schema already documents all eight parameters, including the optional CEP guard and idempotency fields. The description adds some meaning around the exported video and the range/transfer/primaries evidence, but it does not elaborate on the optional guard parameters or sample-time behavior. Baseline 3 is appropriate 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.

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: it samples a caller-owned exported video using existing decoded RGB scopes and declares range/transfer/primaries evidence. It also distinguishes its scope by refusing HDR legal-range claims from an 8-bit RGB proxy and disclaiming Premiere render lineage.

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 description gives clear validity context and explicit exclusions: it applies to a caller-owned exported video sampled through existing decoded RGB scopes, and it refuses HDR legal-range claims from an 8-bit RGB proxy. It also states that it does not prove Premiere render lineage. It does not explicitly route to a sibling tool, but the limitations make the intended use clear.

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