Skip to main content
Glama
huaidj-rufus

huaidj-rufus

by huaidj

preview_export_snapshot

Read-onlyIdempotent

Preview file counts, byte size, and storage space for an independent versioned rekordbox export-metadata snapshot before export; optional analysis, without scanning or copying music.

Instructions

Preview file counts, byte size and storage space for an independent versioned export-metadata snapshot. Analysis is optional; Contents music is never scanned or copied.

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": "preview_export_snapshot"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent and non-destructive, so the safety profile is covered. The description adds genuine scope information beyond that: music contents are never scanned or copied and analysis can be skipped, which tells the agent about cost and side effects. It does not describe how size is computed or what the preview result looks like, keeping it at 3.

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?

Two tight sentences, with the primary action and returned metrics front-loaded and the scope caveat second. The second sentence is compressed to the point of being slightly cryptic ('Contents music is never scanned or copied'), which costs a point.

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 2-parameter read-only tool with no output schema and full annotation coverage, the description is nearly sufficient: it names the metrics and the scope limit. It leaves the meaning of 'analysis' and any cost/performance expectations unstated, which matters given the undocumented include_analysis parameter.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 50% (include_analysis has no schema description), so the description must compensate. 'Analysis is optional' clarifies that include_analysis defaults to a cheap path, and the snapshot framing clarifies what root_path is pointed at. It does not explain what enabling analysis actually adds, leaving a partial 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 a specific verb ('Preview') and resource ('independent versioned export-metadata snapshot') plus the metrics returned: file counts, byte size, storage space. It does not name or distinguish itself from siblings like create_export_snapshot or preview_export_restore, so it stops short of a 5.

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 word 'Preview' implies a non-committal check before creating a snapshot, and 'Analysis is optional' hints at a cheap default path, but the description never states when to call this instead of create_export_snapshot or preview_export_restore, nor any prerequisites for root_path.

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