Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
CRYSTALIZE_FUSERNoThe folder where FUSER is installed, if it is elsewhere than Steam's default library. Alternatively pass --game <folder>.

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{}
prompts
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
get_stateB

The session's key and tempo, the tempo range FUSER allows, each deck's playing and queued disc, and the mix playing, if one is: the bar it is on and the bar its next step is on.

get_setB

In a campaign set: the measure FUSER is on, the open crowd requests with what each wants and the measure it ends on, the goals not yet done with their progress, how many of each are settled, whether the section has a crowd meter, the meter from 0 to 100 and its band (low, medium, high, peak) and warnings, the mix's freshness from 0 to 100, which a new drop raises and a still stretch lets fade, and the score. Measures are FUSER's own, not a mix's bars. A goal's text may keep a placeholder such as {Transition} the mod cannot read yet.

await_eventA

In a campaign set, wait until something happens and say what: a request coming, starting, ending within a few measures, passing or failing; a goal starting, done, or ending undone; the crowd meter coming on or falling below meter_below; the set ending; keep_alive stopping. Returns at once with anything since you last looked, else waits up to seconds, and gives get_set's view of the set with it. Call it between actions instead of polling get_set.

search_songsA

Search the songs you can play, custom songs included and DLC you do not own left out. Returns the total that match and up to limit of them: id, title, artist, year, genre, the song's own BPM and key, its tags, and its discs with name, type and instrument. Instrument, disc type and years find what a crowd request or goal asks for. Works from the saved library while FUSER is closed.

tag_songsB

Write down what songs are like to hear, for every later session to search: energy from 1, a still ballad, to 10, the hardest in the library; style in a few words; what the lyrics are about; and mood_clash when the sound and the words pull opposite ways. Fields given replace those there; clear removes a song's tags.

plan_mixA

Check a mix without playing it. Returns its length and the timeline in segments, each with the bars it covers, the time it starts, the key, tempo and energy, what each deck plays with the pitch shift and stretch FUSER gives it, and checks: two vocals, no beat, no bass, two basses, one song on every deck, pitched far, no version in the session's mode, stretched too far. Checks over the whole mix follow: steps off the phrase, stretches where nothing changes, discs dropped twice, key clashes, tempo and energy jumps. A plan that cannot play is refused with every problem listed.

save_mixA

Save a plan under a name, refusing one plan_mix would refuse. Saving the name again replaces it.

load_mixD

A saved plan, to change and check again.

list_mixesC

The saved mixes, with when each was saved and its number of steps.

play_mixA

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.

stop_mixA

Stop the mix playing. The decks keep playing what they have.

keep_aliveC

In a campaign set, keep the crowd meter from draining while you think: 3 bars after the last change, Crystalize drops one of these discs on its deck, choosing one that makes a mix not heard this session, then the one dropped least, never one already on a deck or one of the last 3 dropped, and never so often the crowd calls it overactive. Give at least 4, and 12 or more keeps the mix fresh, discs that can swap in for each other without spoiling the mix, such as two beats on one deck and two loops on another. It waits while a mix plays or a crowd request is open, leaving the request to you. With stop, it stops.

drop_discA

Play a disc on a deck, replacing what it held, from the next bar. Returns once it is sent, up to a bar later. With queue, it waits on the deck until drop_queue.

drop_queueA

Drop every queued disc together, from the next bar.

ejectC

Stop a deck and take its disc off, at the end of the bar.

take_snapshotA

Save the mix playing as a snapshot, as FUSER's Take Snapshot key does, on the next downbeat, for goals that ask for one. Each is kept in the player's profile.

set_keyA

Change the session's key from the next bar. Every deck follows.

set_tempoA

Change the session's tempo from the next bar, within the range get_state gives.

mute_deckA

Mute or unmute a deck without taking its disc off, from the next bar.

solo_deckB

Solo or unsolo a deck, from the next bar.

Prompts

Interactive templates invoked by user choice

NameDescription
tag_libraryTag FUSER's songs with energy, style and lyrics, in a session that does nothing else
build_mixChoose songs, plan a mix, fix what its checks find, then save and play it
play_setPlay the campaign set FUSER has open, goal by goal and request by request, for as many stars as it gives
review_mixFind and fix the weak parts of a saved mix

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

B3.2/5.0

Scored across 20 tools

Disambiguation5/5

Each tool targets a distinct resource or action: session state vs. campaign set state, mix planning vs. playing vs. stopping, and deck-level controls are clearly separated. Potential overlaps such as get_state/get_set and drop_disc/drop_queue are explicitly differentiated in their descriptions.

Naming Consistency5/5

The tool set uses consistent snake_case verb_noun naming throughout, with clear action prefixes like get_, set_, drop_, save_, load_, list_, and play_. Minor standalone verb names like eject are still readable and fit the deck-control context.

Tool Count4/5

The 20 tools cover several genuinely distinct areas: live session control, campaign sets, song tagging/search, and mix planning/persistence. The count is on the high side but largely earned by the breadth of the DJ/mixing domain.

Completeness4/5

The surface covers most core workflows: song search/tagging, mix planning/saving/loading/playing/stopping, deck manipulation, campaign monitoring, and snapshots. A notable minor gap is the absence of a delete or remove tool for saved mixes.

Maintenance

ActivityNo data
ResponsivenessOutdated data