rekordbox-mcp

Overview Schema Source Related Servers Discussions Admin

get_library_stats

Retrieve comprehensive statistics for your Rekordbox library to analyze track counts, playlist sizes, and overall collection health.

Instructions

Get comprehensive library statistics.

Returns: Dictionary containing various library statistics

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

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 2, 2026

TDQS

C2.9/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavior disclosure. It only mentions that the tool returns a dictionary, which is redundant with the output schema, and gives no insight into side effects, permissions, or the nature of the statistics.

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?

The description is short and front-loaded, but the second sentence about returning a dictionary is partially redundant given the output schema. The use of 'comprehensive' and 'various' adds fluff without precision, but overall it stays concise.

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?

Given the tool has no parameters and an output schema exists, the description does not need to explain return values in detail. However, it fails to specify what 'library statistics' entails or how this tool differs from sibling tools like analyze_library, leaving an ambiguous scope for a simple but potentially overlapping tool.

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?

The tool has zero parameters, so the baseline is 4. The schema is empty and the description does not need to explain parameter semantics; the lack of parameters makes this dimension non-applicable and the baseline applies.

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

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states the tool 'gets' 'library statistics', which is a specific verb and resource, but 'comprehensive' and 'various' are vague qualifiers that do not clarify what statistics are included. It does not differentiate from sibling tools like analyze_library, which could overlap in purpose.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance on when to use this tool versus alternatives. The description does not mention any distinguishing use cases, prerequisites, or situations where this tool is preferred over siblings like analyze_library or get_history_stats.

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