Skip to main content
Glama
huaidj-rufus

huaidj-rufus

by huaidj

inspect_export_library

Read-onlyIdempotent

Inspect known rekordbox USB-export metadata candidates and markers to see what is present on a USB root or local copy without opening a master database or removing broken-library flags.

Instructions

Inspect only known rekordbox USB-export metadata candidates and markers. Presence is not full database validation; never opens a desktop master database or removes a broken-library marker.

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

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/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, so the negative guarantees largely restate them. The description does add two genuinely useful points beyond annotations: that presence of metadata is not full database validation, and that a broken-library marker is left in place, which shapes how the agent should interpret results.

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 tightly written sentences with the scope constraint front-loaded and no filler. The semi-colon structure is dense but readable; minor cost is that the compressed phrasing leaves terms like 'markers' and 'candidates' unexplained.

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?

With no output schema, the description must convey what an inspection yields, and it only obliquely does so via the 'not full database validation' caveat. Combined with the undocumented hash_databases flag, an agent could invoke it correctly but would not fully know what to expect back.

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

Parameters2/5

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

Schema coverage is 50%: root_path is documented in the schema, but hash_databases has no description anywhere, and the tool description says nothing about what it does or when to enable it. This leaves half the parameter surface unexplained.

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 names a specific verb and resource ('inspect ... rekordbox USB-export metadata candidates and markers') and draws a boundary against desktop master databases, which separates it from database-editing siblings. However, 'candidates and markers' is left undefined, so the agent knows the domain but not exactly what gets inspected.

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 'only' plus 'never opens a desktop master database' implies this is a read-only scouting step before snapshot/restore tools, but no explicit when-to-use instruction or named alternative (e.g. create_export_snapshot) is given. Usage is inferable rather than stated.

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