Skip to main content
Glama
leancoderkavy

Premiere Pro MCP Server

by leancoderkavy
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Verify Delivery File

verify_delivery_file

Verify exported delivery files by checking non-empty regular file status and computing SHA-256 or SHA-512 checksums. Compare against expected size and checksum to confirm integrity.

Instructions

Verify that an exported delivery is a non-empty regular file and calculate a SHA-256 or SHA-512 checksum; optionally compare expected size and checksum

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
output_pathYesFull path to the exported delivery file
expected_checksumNoOptional expected hexadecimal checksum to compare
checksum_algorithmNoChecksum algorithm (default: sha256)
minimum_size_bytesNoMinimum acceptable file size in bytes (default: 1)
expected_size_bytesNoOptional exact expected file size in bytes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
okYesWhether the tool completed successfully.
dataNoTool-specific result data when ok is true.
toolYesThe registered MCP tool name.
errorNoFailure detail when ok is false.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.14.4
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "additionalProperties": false,
+  "properties": {
+    "data": {
+      "description": "Tool-specific result data when ok is true."
+    },
+    "error": {
+      "description": "Failure detail when ok is false.",
+      "type": "string"
+    },
+    "ok": {
+      "description": "Whether the tool completed successfully.",
+      "type": "boolean"
+    },
+    "tool": {
+      "description": "The registered MCP tool name.",
+      "minLength": 1,
+      "type": "string"
+    }
+  },
+  "required": [
+    "ok",
+    "tool"
+  ],
+  "type": "object"
+}
  2. Addedv1.4.0

TDQS

A4.5/5.0
Behavior4/5

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

The description adds concrete behavioral detail beyond annotations: it states the file must be non-empty and a regular file, that a checksum is calculated, and that expected size/checksum may be compared. Annotations do not claim read-only, and the description doesn't contradict them; it simply doesn't discuss side effects, but the verification semantics are clear.

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?

One well-structured sentence that front-loads the core purpose and packs in the essential behaviors without redundancy. Every clause adds information needed to understand or invoke the tool.

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

Completeness5/5

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

With 100% schema parameter coverage and an output schema present, the description covers the full verification behavior: file type/size check, checksum calculation, and optional comparisons. No critical information needed for correct invocation is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so this dimension starts at baseline 3. The description adds extra meaning by tying parameters to the verification workflow: expected_size_bytes and expected_checksum are for optional comparison, checksum_algorithm selects SHA-256/SHA-512, and minimum_size_bytes corresponds to the non-empty file check. This goes beyond the schema's field-level descriptions.

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 uses a specific verb ('Verify') and a specific resource ('exported delivery'), and spells out the exact checks performed: non-empty regular file, SHA-256/SHA-512 checksum, and optional size/checksum comparison. This makes it clearly distinguishable from sibling validation tools such as validate_export_preset or verify_fcpxml_media_references.

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 use case is clear: verify a delivery file after export, optionally checking against expected values. It doesn't explicitly name when-not-to-use or list alternatives, but the action and resource are specific enough that an agent can select it over related validation and export tools without ambiguity.

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