Skip to main content
Glama

archive_project

Archive a DaVinci Resolve project into a .dra folder with optional source media, render cache, and proxy media to preserve a project backup.

Instructions

Archive a project to a .dra folder, optionally with source media, render cache and proxies.

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": {
      "name": "<name>",
      "path": "<path>"
    },
    "name": "archive_project"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
pathYes
proxy_mediaNo
render_cacheNo
source_mediaNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds that output goes to a .dra folder and that media/cache/proxies can be bundled, but says nothing about whether an existing archive at the destination is overwritten, disk-space implications, or whether the project must be open first.

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?

A single front-loaded sentence with no filler or redundancy. It is efficient, though the brevity comes at the cost of the missing guidance noted elsewhere.

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

Completeness2/5

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

For a five-parameter write operation with no output schema and zero schema description coverage, the description is thin: it omits the meaning of both required parameters, the return/confirmation behavior, and failure modes. The agent could guess at the booleans but would likely have to experiment with name and path.

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

Parameters2/5

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

Schema description coverage is 0%, so the description carries the full burden, yet it only loosely names the three optional booleans (source media, render cache, proxies). The two required parameters, name and path, are never explained — it is unclear whether name is the archive name or project name and whether path is a destination directory or full archive path.

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 verb and resource (archive a project) plus the output artifact type (.dra folder) and optional inclusions. It is clear what the tool does, but it never distinguishes itself from plausible siblings such as export_project, save_project, or cloud_project.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance and no exclusions; the agent is not told how archiving differs from exporting, saving, or uploading to cloud. The only hint is the optional-content list, which implies a self-contained bundle but does not say when that is preferable.

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