Skip to main content
Glama
huaidj-rufus

huaidj-rufus

by huaidj

rekordbox_version_advice

Read-onlyIdempotent

Read official version-specific USB export advisories and main-library versus export-library compatibility guidance to plan rekordbox media preparation.

Instructions

Read official version-specific USB export advisories and main-library versus export-library compatibility guidance. Does not infer a producer version from filenames or promise database repair.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "rekordbox_version_advice"
  }
}

Input Schema

NameRequiredDescriptionDefault
scopeNousb-export
versionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world behavior, so the description does not need to restate the safety profile. What it adds is source authority ('official') and explicit negative guarantees that prevent the agent from over-trusting the output as a version detector or a repair promise; it says nothing about the volume or freshness of advisories returned.

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?

Two sentences with no filler: the positive scope leads, and the disclaimer about what it will not do follows immediately. Nothing is repeated from the schema or annotations.

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, read-only, zero-required-argument lookup tool, this is nearly sufficient; the negative guarantees cover the main misuse risks. Because there is no output schema, the description would ideally sketch the shape of the advisories returned, which is the only remaining gap.

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 description coverage is 0%, so the description must compensate. It does so partly: the 'USB export' and 'main-library versus export-library' wording maps naturally onto the scope enum values (usb-export, desktop-main-library, all), and 'version-specific' signals the version parameter. It never states the default scope behavior or what happens when version is omitted, and the enum's 'all' value is not addressed.

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 gives a specific verb ('Read') and specific resources ('version-specific USB export advisories' and 'main-library versus export-library compatibility guidance'), so an agent knows exactly what kind of content comes back. It does not explicitly name a sibling to distinguish itself from, but the advisory/guidance framing is distinct from tools like check_dj_audio or filesystem_compatibility.

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?

Usage is implied by the resource named ('advisories', 'compatibility guidance') rather than spelled out: there is no statement of when to call this versus dj_model_compatibility or filesystem_compatibility. The negative scope sentence ('does not infer a producer version from filenames or promise database repair') usefully rules out two expectations but is not when-to-use guidance.

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