Skip to main content
Glama
huaidj-rufus

huaidj-rufus

by huaidj

preview_export_restore

Validates a complete snapshot and previews same-media export-metadata restoration, returning a short-lived preview ID and exact snapshot identity without restoring analysis/music or main libraries.

Instructions

Validate a complete snapshot and preview same-media export-metadata restoration. Returns a short-lived preview ID and exact snapshot identity. Analysis/music and main libraries are not restored.

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>"
    },
    "name": "preview_export_restore"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations declare not-read-only, non-destructive, non-idempotent, closed-world, but leave the agent guessing what the tool actually does. The description fills that gap well: it validates, produces a short-lived preview ID, returns exact snapshot identity, and explicitly limits restoration scope — real behavioral context beyond the structured fields, though it omits the preview's lifetime and failure behavior.

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?

Three short sentences, front-loaded with the core action, then return values, then the scope caveat. No filler or repetition of the name.

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 two-parameter, non-read-only tool with no output schema, the description covers what it does, what it returns (preview ID, snapshot identity), and what it will not restore. Missing only the preview's lifetime and preconditions, which are minor against the rest.

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 50%: root_path is documented in the schema, while snapshot_id carries just a uuid format and no prose. The description's phrase 'exact snapshot identity' loosely ties to snapshot_id but adds no format, source, or validation semantics, so it neither compensates for nor fully ignores the gap.

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 specific verbs and resources: validating a complete snapshot and previewing same-media export-metadata restoration. It implicitly distinguishes itself from the sibling preview/restore tools by naming the restoration scope, though it never names an alternative directly.

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 exclusion clause ('Analysis/music and main libraries are not restored') gives useful scoping guidance about what this preview covers. However, it never says when to pick this over preview_export_snapshot or restore_export_snapshot, nor what prerequisite state is required to run it.

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