Skip to main content
Glama
huaidj-rufus

huaidj-rufus

by huaidj

create_export_snapshot

Create a verified, versioned local snapshot of PIONEER/rekordbox metadata and sidecars, optionally backing up USBANLZ analysis, without changing source media. Stop rekordbox first.

Instructions

Copy complete PIONEER/rekordbox metadata including sidecars into a new local versioned snapshot with verified hashes. Requires rekordbox stopped. Optionally backs up USBANLZ analysis for preservation; music is excluded. Does not change source media.

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": {
      "root_path": "<root_path>"
    },
    "name": "create_export_snapshot"
  }
}

Input Schema

NameRequiredDescriptionDefault
root_pathYesAbsolute selected USB root or an ordinary local copy containing PIONEER/rekordbox.
exporter_versionNo
include_analysisNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior4/5

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

The annotations already declare readOnlyHint=false and destructiveHint=false, and the description adds real value on top: the rekordbox-must-be-stopped precondition, the explicit exclusion of music, and the reassurance that source media is untouched. It stops short of explaining what happens on repeated calls (relevant given idempotentHint=false) or where the snapshot is written, but the added context is substantial.

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 tight sentences with the core operation front-loaded and constraints following in descending importance. Almost no waste; the only near-redundancy is 'Does not change source media,' which restates the destructiveHint=false annotation, though it usefully reinforces it in plain language.

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 write tool with no output schema, the description covers preconditions and exclusions well but omits two things an agent needs: where the snapshot is written (only root_path is in the schema) and what the call returns. The exporter_version parameter is also unexplained, so the definition is workable but not fully self-sufficient.

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 coverage is only 33%, so the description needs to carry weight. It does clarify the optional analysis flag ('Optionally backs up USBANLZ analysis for preservation; music is excluded'), which maps to include_analysis. But exporter_version goes entirely unmentioned in both schema and description, leaving one parameter semantically opaque.

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 opens with a specific verb and resource: 'Copy complete PIONEER/rekordbox metadata including sidecars into a new local versioned snapshot with verified hashes.' That makes the operation and its output tangible. It does not name or contrast against the closest siblings (preview_export_snapshot, restore_export_snapshot), so differentiation is left to inference from the word 'new'.

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?

It states one hard precondition, 'Requires rekordbox stopped,' which is genuinely useful selection guidance. However, it never says when to choose this over preview_export_snapshot or restore_export_snapshot, nor does it suggest previewing first, so the when-to-use layer is only implied.

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