Mixx-DJ-MCP

Overview Schema Source Related Servers Discussions Admin

mixx_history

Track DJ play history, log transitions, and analyze your style profile. Suggest tracks you haven't played recently to refine sets.

Instructions

DJ play history, analytics, and personal style profiling.

PORTMANTEAU PATTERN: Consolidates analytics and history.

SUPPORTED OPERATIONS:

plays: Recent play history
transitions: Recent transition log
profile: Personal DJ style profile (BPM range, key preferences, transition style)
suggest: Tracks you haven't played recently
log_play: Manually log a track play (auto-called by deck ops)
log_transition: Manually log a transition

Examples: mixx_history("profile") mixx_history("suggest", limit=10) mixx_history("plays", limit=20)

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": {
      "operation": "<operation>"
    },
    "name": "mixx_history"
  }
}

Input Schema

Name	Required	Default
`deck`	No
`limit`	No
`to_deck`	No
`from_deck`	No
`operation`	Yes
`track_path`	No
`track_title`	No
`track_artist`	No
`transition_type`	No	filter_sweep

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Sep 27, 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. For a tool with six operations including mutations (log_play, log_transition), it says nothing about side effects, reversibility, permissions, or whether logging requires an existing track. The 'suggest' and 'profile' operations are opaque in terms of behavior.

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?

Structured as a header, portmanteau note, bulleted operations, and examples. Front-loaded and scannable. The 'PORTMANTEAU PATTERN' line is slightly jargon-y but short, and the operation list earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values needn't be explained, which helps. But with no annotations and 0% parameter coverage, the description leaves key behaviors (side effects of logging operations, permissions, parameter meanings) undocumented, which is inadequate for a 9-param, 6-operation tool with mutations.

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 description coverage is 0% and 9 parameters exist. The description mentions 'limit' in examples and ties some operations to decks implicitly, but never explains deck, to_deck, from_deck, track_path, track_title, track_artist, or transition_type semantics. With a low-coverage schema, the description had an obligation to compensate and largely does not.

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+resource: 'DJ play history, analytics, and personal style profiling' with an explicit operation list. Distinguishes itself from siblings like mixx_library or mixx_transition by consolidating history/analytics, though sibling differentiation is implicit rather than named.

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 operation list implies when each mode applies, and mention that log_play is 'auto-called by deck ops' hints at manual vs automatic use. But there's no explicit when-not-to-use guidance or routing to sibling tools for overlapping concerns.

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