Skip to main content
Glama

clone_media

Offload camera-card media by copying a source directory to one or more target directories with checksum verification, progress tracking, and cancellation.

Instructions

Clone tool (camera-card offload with verification). 'settings' sets preserve_folder_name and checksum (CLONE_CHECKSUM_TYPE_NONE/FILESIZE/CRC32/MD5/SHA256/SHA512/XXH_64); 'start' copies source_dir to target_dirs; 'status' reports progress; 'stop' cancels.

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": {
      "action": "<action>"
    },
    "name": "clone_media"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionYes
checksumNo
source_dirNo
target_dirsNo
preserve_folder_nameNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare non-read-only, non-destructive, closed-world, so the safety floor is set structurally. The description adds the checksum algorithm set and that start fans out to multiple target_dirs, which is real added context. However, it is silent on the highest-risk unknown for a clone tool: whether existing content in target_dirs is overwritten, whether start is synchronous, and what stop leaves behind.

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?

Front-loads the identity of the tool in the first clause, then switches to a compact semicolon-delimited action map. Nearly every clause earns its place; only the raw enum constant prefix is slightly noisy.

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 mutating 5-parameter tool with no output schema and no annotation detail on permissions, the description covers action semantics but not return values (what 'status' reports), blocking behavior, or target-overwrite handling. Adequate to invoke, incomplete for confident operation.

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 must carry the load, and it partially does: it enumerates the legal checksum values (CLONE_CHECKSUM_TYPE_NONE/FILESIZE/CRC32/MD5/SHA256/SHA512/XXH_64) which the schema only exposes as a bare string, and it binds source_dir/target_dirs to the 'start' action and preserve_folder_name to 'settings'. It omits which parameters are required per action and any path format expectations.

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 plus scope: 'Clone tool (camera-card offload with verification)', then enumerates the four actions with a one-line function each. Very clear what the tool does, though it does not differentiate itself from siblings like import_media or link_clip_media.

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?

The per-action breakdown ('settings' configures, 'start' copies, 'status' reports, 'stop' cancels) gives an implied operating sequence, which is more than none. It never states prerequisites (must settings be run before start?), nor when to use this instead of the import/link siblings, so guidance remains implicit.

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