Skip to main content
Glama

Build Project Handoff Manifest

build_project_handoff_manifest
Read-onlyIdempotent

Validates explicitly listed dependencies in an approved workspace and reports missing files, byte counts, source identity, and unresolved nested or template assets for handoff.

Instructions

Inspect explicitly listed dependencies inside an approved consolidated workspace. Reports observed bytes, missing files, expected source identity and unresolved nests/image sequences/AE/template dependencies. A copied project alone cannot pass completeness.

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": {
      "approved_workspace_path": "<approved_workspace_path>",
      "dependencies": "<dependencies>",
      "inventory_complete": "<inventory_complete>"
    },
    "name": "build_project_handoff_manifest"
  }
}

Input Schema

NameRequiredDescriptionDefault
dependenciesYesExpected dependencies, at most500.
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.
inventory_completeYesWhether upstream dependency enumeration is complete, including nested/external sources.
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.
approved_workspace_pathYesExisting absolute approved root; symlink escapes reject.

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.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true and closed-world, so the safety profile is covered. The description adds real behavioral content beyond that: it inspects only enumerated dependencies, reports observed bytes versus expected, flags missing files and unresolved nests/image sequences/AE/template dependencies, and asserts that a copied project alone cannot satisfy completeness. It stops short of saying whether incomplete results are returned as data or raised as errors.

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 core action and immediately followed by what is reported. The closing caveat 'A copied project alone cannot pass completeness' earns its place as a warning, though it is terse enough to be slightly cryptic without the surrounding context.

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

Completeness3/5

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

The tool is complex — six parameters, nested CEP identity objects, and an output schema — and the description covers the what and the checks but not the semantics of inventory_complete, the failure/partial-result behavior, or the difference between a passing and failing manifest. Because an output schema exists, the return shape need not be explained, but the completeness gate is central enough that leaving its mechanics implicit is a real gap.

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 baseline is 3. The description adds marginal interpretation — 'explicitly listed' for dependencies, 'approved' for the workspace root, 'expected source identity' for the CEP guard — but does not explain how inventory_complete changes the outcome, which is the one parameter an agent could easily mis-set.

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 action on a specific resource: inspect explicitly listed dependencies inside an approved consolidated workspace, and reports observed bytes, missing files, and unresolved nested/image-sequence/AE/template dependencies. That is concrete enough to distinguish it from pure project-listing or audit tools, though the description never names a sibling alternative and 'inspect/report' sits slightly at odds with the 'build manifest' name.

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 implied rather than stated: the phrase 'explicitly listed dependencies' signals it does not discover dependencies itself, and 'approved consolidated workspace' implies a prior approval/consolidation step. There is no explicit when-to-use, when-not-to-use, or named alternative among the many build_*/audit_* siblings.

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