Skip to main content
Glama

project_snapshot

Save and export the current DaVinci Resolve project as a .drp backup before risky edits, then restore it later with project_import.

Instructions

Save and export the current project to a .drp file (backup before risky edits). Restore later with project_import. Files go to ~/Documents/ResolveMCP/snapshots.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "project_snapshot"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
with_stills_and_lutsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries full behavioral burden. It discloses the output format (.drp) and destination folder, plus its role as a backup, which is useful. However, it omits overwrite behavior, permission or side-effect details, and what the returned result looks like.

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 definition is three short, front-loaded statements. The primary action comes first, followed by the restore path and file location. Every sentence adds concrete value with no wasted wording.

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?

For a two-optional-parameter snapshot tool with no annotations or output schema, the description covers the operation, purpose, and file destination. However, it leaves both parameters unexplained, including the meaning of 'name' and the default-included stills/LUTs behavior. That is enough for a default invocation but incomplete for informed parameter use.

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

Parameters1/5

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

Schema description coverage is 0%, so the description should compensate for the two undocumented parameters. It never mentions 'name' or 'with_stills_and_luts' and adds no meaning about how either affects the snapshot. This leaves both parameters completely unexplained beyond their bare schema names.

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?

The description states a specific verb and resource: save/export the current project to a .drp file. It also establishes the backup use case and the restore counterpart, project_import. It does not clearly distinguish itself from siblings like project_export or save, preventing a 5.

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 a clear usage scenario: backup before risky edits. It also routes the user to project_import for restoring later. It does not address when to use this versus save or project_export, so it lacks explicit alternatives.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.