Skip to main content
Glama
huaidj-rufus

huaidj-rufus

by huaidj

restore_export_snapshot

Destructive

Restores a reviewed export-metadata snapshot to a specified USB. It preserves displaced metadata in quarantine and requires explicit confirmation plus a matching snapshot digest.

Instructions

DESTRUCTIVE TO CURRENT EXPORT METADATA: restore the reviewed snapshot to the same identified USB while preserving displaced metadata in quarantine. Requires explicit authorization, preview and matching snapshot digest; does not rewrite master databases, music or analysis and does not promise corruption repair.

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>",
      "snapshot_id": "<snapshot_id>",
      "preview_id": "<preview_id>",
      "expected_snapshot_identity": "<expected_snapshot_identity>",
      "confirmation": "<confirmation>",
      "confirm_restore": "<confirm_restore>"
    },
    "name": "restore_export_snapshot"
  }
}

Input Schema

NameRequiredDescriptionDefault
root_pathYesAbsolute selected USB root or an ordinary local copy containing PIONEER/rekordbox.
preview_idYes
snapshot_idYes
confirmationYes
confirm_restoreYes
expected_snapshot_identityYesExpected SHA-256 obtained from a trusted publisher or an explicitly selected local image.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the destructiveHint annotation, the description specifies exactly what is affected: current export metadata is displaced into quarantine. It also discloses required authorization/preview/digest checks and clarifies what the tool will not do, including rewriting master data or repairing corruption.

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 description is front-loaded with the destructive warning and then packs only relevant clauses about preservation, prerequisites, and scope exclusions. It is dense but well structured, with no filler.

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

Completeness4/5

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

For a destructive, six-parameter operation with no output schema, the definition covers the main safety profile, prerequisites, and scope limits. It still leaves key parameter roles somewhat implicit, but an agent can understand the operational boundaries and required conditions.

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 only 33%, so the description carries more burden. It adds useful meaning for preview, snapshot review, and digest matching, but it does not clearly distinguish snapshot_id from preview_id or explain confirmation versus confirm_restore.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/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: restore the reviewed snapshot to the same identified USB. It also scopes the action as destructive to current export metadata and distinguishes the operation from snapshot creation or preview by referring to a reviewed snapshot, preview, and matching digest.

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 clear preconditions: explicit authorization, a preview, and a matching snapshot digest are required before restore. It also states important exclusions, such as not rewriting master databases, music, or analysis, but it does not explicitly name the preview or snapshot-creation siblings as alternatives.

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