Skip to main content
Glama
Sign In
Crystalize

Crystalize

by Peyton-C
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

play_mix

Play a saved mix or bar-by-bar FUSER plan, stopping any current mix and clearing unused decks at bar 0 before steps begin.

Instructions

Play a saved mix or a plan in FUSER, each step on its bar, stopping any mix already playing. Decks the plan does not fill at bar 0 are emptied first. Returns at once; get_state follows it. Needs a freestyle session or a campaign set.

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

Input Schema

NameRequiredDescriptionDefault
bpmNoThe opening tempo
keyNoThe opening key, Ab for A flat major, Abm for minor
mixNoA saved mix, in place of a plan
stepsNoWhat happens on which bar. Steps on one bar happen together
end_barNoThe bar the mix ends on. Defaults to 16 after the last step

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses that playback is interrupted, that unfilled decks are emptied at bar 0 (a destructive side effect on existing deck contents), and that the call is non-blocking ('Returns at once'). It omits error/failure behavior and whether playback can be aborted mid-plan.

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?

Four short sentences, front-loaded with the action and followed by side effects, return behavior, and prerequisites. Dense and mostly waste-free; the phrasing is slightly compressed but never padded.

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?

No annotations and no output schema, so the description must cover safety and prerequisites, which it does (session requirement, deck clearing, non-blocking return). Only failure modes and any rate/session constraints are missing, which is a minor gap for this 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?

Schema coverage is 100%, so baseline is 3, but the description adds cross-parameter meaning: bpm/key are the opening values, steps fire on their bar, and decks not covered by the plan are cleared at bar 0. That interaction between steps, decks, and end-of-mix behavior is not fully conveyed by the schema alone.

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 and resource (play a saved mix or a plan) and clarifies the timing model ('each step on its bar'). It is distinguishable from plan_mix/save_mix/list_mixes by naming the two input modes, though it does not explicitly name the sibling that produces the plan.

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

Usage Guidelines4/5

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

Gives the prerequisite ('Needs a freestyle session or a campaign set') and directs the follow-up call ('get_state follows it'). It implies replacement semantics ('stopping any mix already playing') but never explicitly contrasts with stop_mix, drop_disc, or plan_mix as alternatives.

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

Deploy Server

Other Tools