Skip to main content
Glama

encrypt_dctl

Encrypts .dctl files into .dctle format with optional expiry date, output name, and folder, enabling controlled distribution of DaVinci Resolve control files.

Instructions

Encrypt a .dctl file into a .dctle (optional output name, expiry date and output folder).

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": {
      "input_path": "<input_path>"
    },
    "name": "encrypt_dctl"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
expiryNo
input_pathYes
output_folderNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

Annotations declare readOnlyHint=false, destructiveHint=false, and openWorldHint=false, so safety profile is partly covered, but the description adds nothing beyond the annotations. It does not explain what the expiry date does (expiration of decryption rights?), whether an existing output file is overwritten, what permissions or keys are needed, or what the resulting .dctle contains.

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 the core action first and optional parameters parenthesized. No filler, though the parenthetical is terse enough that it trades clarity for brevity.

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?

This is a mutating file-production tool with no output schema and no annotation for return values, yet the description never says what is returned or where the encrypted file lands by default. Combined with zero schema coverage, key behavioral facts an agent needs before invoking it are missing.

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 0%, so the description carries the burden of explaining four parameters. It maps three optional ones (name, expiry, output_folder) to their roles, which adds meaning beyond bare titles, but leaves the expiry string format, default naming behavior, and output_folder path semantics unspecified, and says nothing about input_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 pair: encrypt a .dctl file into a .dctle, including the format transformation. It does not distinguish itself from siblings such as validate_dctl, but the operation (encryption, producing a new file type) is concrete enough that an agent can identify it.

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, no prerequisites (e.g., must the file exist, must it be unlocked or validated first), and no mention of alternatives or exclusions. The agent must infer the appropriate context entirely from the tool name.

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